Systemd commandline output

Question

Dear Folks,
If I have e.g. a config error in my sshd_config running by hand
systemctl restart sshd.service
gives me no message wether the daemon was able to start or not.
But running stop followed by a start gives me:
systemctl stop sshd.service
systemctl start sshd.service
Job for sshd.service failed. See "systemctl status sshd.service" and "journalctl -xe" for details.
How can I turn on this behaviour by default. It is quite annoying to always run 'status' after a restart just to check if there was a problem. Even more if a start shows me the message in the terminal.
Thx

Answer 1

gaelic wrote:
Dear Folks,
If I have e.g. a config error in my sshd_config running by hand
systemctl restart sshd.service
gives me no message wether the daemon was able to start or not.
But running stop followed by a start gives me:
systemctl stop sshd.service
systemctl start sshd.service
Job for sshd.service failed. See "systemctl status sshd.service" and "journalctl -xe" for details.
How can I turn on this behaviour by default. It is quite annoying to always run 'status' after a restart just to check if there was a problem. Even more if a start shows me the message in the terminal.
Thx
Well, bug people at systemd-devel ML... I would do it myself, but I think there is little point because systemd's error reporting is terrible anyway (there are many other "quircks" like the one you found). For example, "job for sshd.service failed" does not mean that "sshd failed to start". So, when starting a new service, I'd suggest to not rely on systemctl no matter what it says (or doesn't say), but always check ps(1) and logs.
Last edited by Leonid.I (2015-01-16 19:40:49)