Bug#891836: systemd: systemctl start/stop/restart valid-template at invalid-instance doesn't cause errors
Michael Biebl
biebl at debian.org
Thu Mar 1 14:10:26 GMT 2018
Control: tags -1 + moreinfo unreproducible
Am 01.03.2018 um 13:24 schrieb Martin von Wittich:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: normal
> Tags: upstream
>
> Dear Maintainer,
>
> the following commands unexpectedly do not print any error messages or
> return non-zero exit codes:
>
> martin.mein-iserv.de ~ # systemctl stop postgresql at does-not-exist
> martin.mein-iserv.de ~ # systemctl start postgresql at does-not-exist
> martin.mein-iserv.de ~ # systemctl restart postgresql at does-not-exist
>
I can't reproduce this, neither on v237 nor on v232:
# systemctl stop postgresql at does-not-exist
Failed to stop postgresql at does-not-exist.service: Unit
postgresql at does-not-exist.service not loaded.
# systemctl start postgresql at does-not-exist
Failed to start postgresql at does-not-exist.service: Unit
postgresql at does-not-exist.service not found.
# systemctl restart postgresql at does-not-exist
Failed to restart postgresql at does-not-exist.service: Unit
postgresql at does-not-exist.service not found.
--
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/20180301/68268e52/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list