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

[Michael Biebl]

Am 02.03.2018 um 17:23 schrieb Christoph Berg:
> Re: Michael Biebl 2018-03-02 <4c3431e8-36e3-d86b-4bb8-1f99eaa38fce at debian.org>
>> Am 02.03.2018 um 13:45 schrieb Christoph Berg:
>>
>>> I agree that it is not helpful that it doesn't raise an error here,
>>> but I think it is working as intended by systemd. Or should we rather
>>> be using AssertFileExists here? But starting the non-existing "foo"
>>> service doesn't put "foo" into a permanent error state either.
>>
>> Why not just drop the Condition altogether?
>> This way you'd get a proper error message from posgresql, and it would
>> be easier to diagnose what's going wrong?
> 
> For the same reason that "systemctl start nonexisting.service" doesn't
> permanently leave nonexisting.service in a error state that is visible
> e.g. via "systemctl". I'd think that would be worse.

Not sure what you mean by that. Can you elaborate?



-- 
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/20180302/5afd5f2f/attachment-0002.sig>