"systemctl status foo.service" ought to have an error message that the unit file is broken. However, comments in ExecStart= are just passed on verbatim to whatever you execute, so this should reflect in some specific error message? I. e. if I have
$ cat /etc/systemd/system/broken.service [Service] ExecStart=/bin/sleep 1 # muhaha $ sudo systemctl daemon-reload $ sudo systemctl start broken.service $ systemctl status broken.service ● broken.service Loaded: loaded (/etc/systemd/system/broken.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2015-06-02 12:39:05 CEST; 7s ago Process: 12139 ExecStart=/bin/sleep 1 # muhaha (code=exited, status=1/FAILURE) Main PID: 12139 (code=exited, status=1/FAILURE) Jun 02 12:39:05 donald systemd[1]: Started broken.service. Jun 02 12:39:05 donald systemd[1]: Starting broken.service... Jun 02 12:39:05 donald sleep[12139]: /bin/sleep: ungültiges Zeitintervall »#“ Jun 02 12:39:05 donald systemd[1]: broken.service: main process exited, code=exited, status=1/FAILURE Jun 02 12:39:05 donald sleep[12139]: /bin/sleep: ungültiges Zeitintervall »muhaha“ Jun 02 12:39:05 donald sleep[12139]: „/bin/sleep --help“ liefert weitere Informationen. Jun 02 12:39:05 donald systemd[1]: Unit broken.service entered failed state. Jun 02 12:39:05 donald systemd[1]: broken.service failed. which seems quite clear? (Sorry for the German error messages, they basically say "invalid time interval") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448656 Title: systemd doesn't allow proper shutdown after it encountered errornous .service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448656/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
