Control: tags -1 moreinfo unreproducible
Am 01.03.2018 um 16:00 schrieb Martin von Wittich:
> Hi Michael,
>
> On Thu, 1 Mar 2018 15:10:26 +0100 Michael Biebl <bi...@debian.org> wrote:
>> I can't reproduce this, neither on v237 nor on v232:
>>
>> # systemctl stop postgresql@does-not-exist
>> Failed to stop postgresql@does-not-exist.service: Unit
>> postgresql@does-not-exist.service not loaded.
>>
>> # systemctl start postgresql@does-not-exist
>> Failed to start postgresql@does-not-exist.service: Unit
>> postgresql@does-not-exist.service not found.
>>
>> # systemctl restart postgresql@does-not-exist
>> Failed to restart postgresql@does-not-exist.service: Unit
>> postgresql@does-not-exist.service not found.
>
> Do you have a postgresql template installed (should be the case when you
> have a postgresql-9.{4,6} (jessie/stretch) server package installed)? If
> not, try another template, maybe getty (I hope that's available on every
> system, would make reproducing this a lot easier):Hm, right. I completely missed the part about "valid-template", and no, I didn't have postgresql@.service. But I'm not sure if what you are seeing is actually a bug. A templated service does not necessarily need a representation on disk. It is very much possible, that you simply want to pass a command flag to a daemon for example. So systemd will happily start/stop/restart such a noop in your case. The only case where it fails is, on a reload, because there wasn't actually a process running which could be reloaded. Sounds a bit strange but is imho consistent. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
