Bug#891836: systemd: systemctl start/stop/restart valid-template at invalid-instance doesn't cause errors

[Michael Biebl]

Am 02.03.2018 um 20:48 schrieb Christoph Berg:

> "systemctl start foo.service" throws an error, but does not mark
> foo.service as failed.
> 
> If "systemctl start postgresql at foo.service" would not have
> ConditionFileExists, it would permanently be marked as failed (until
> "systemctl reset-failed").
> 
> Both should behave the same in the sense that typoing the service name
> on start shouldn't leave the system in a degraded state. (It would be
> nice if "systemctl start postgresql at foo.service" would throw a
> one-time error, but it doesn't look like that could be achieved.)

Well, I don't think those two cases are the same and as such should be
treated equally by systemd.
I see typoing the template name more like adding a typo to
ExecStart=/sbin/foobard /etc/typo_in_file_name
In this case foobard would most likely fail to start and systemd would
mark the service as failed. This is more comparable to your case,
because the template name is passed as a config option to the service


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180303/6e753238/attachment-0002.sig>