service --status-all reports some service status lines on stdout, others on stderr.
noticable and poblematic especially when piping to less/grep/etc.
presumably this is because it's calling multiple individual scripts each generating their own to inconsistent destinations.
workaround is to remember to 2>&1, but that is dumb; if the scripts can't be made consistent then perhaps at least service(8) can at least do this internally?
service --status-all reports some service status lines on stdout, others on stderr.
noticable and poblematic especially when piping to less/grep/etc.
presumably this is because it's calling multiple individual scripts each generating their own to inconsistent destinations.
workaround is to remember to 2>&1, but that is dumb; if the scripts can't be made consistent then perhaps at least service(8) can at least do this internally?
12.04 current dist-upgrade as of today