On Thu, Jun 29, 2017 at 11:51:53AM +0200, Oliver Neukum wrote: > Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald: > > > > Am 29.06.2017 um 10:05 schrieb Oliver Neukum: > > > > > > Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering: > > > > > > > > Well, it's a service manager. As such it keeps track of services, > > > > knows when they are started and when they aren't. Why would it stop > > > > services that aren't started? > > > > > > Because you command it to do so. > > > The check systemd does adds no value. There is a reason to not start > > > something that is running. The reverse does not apply > > > > this is nonsense - how in the world should systemmd know what to stop > > when it has no clue about the involved processes because it did not > > start the service and hence has no tracking at all > > > > So try and fail. That is still no excuse for ruling out that you can > stop a service you have not started. That is pure politics.
There's no service if it wasn't started by systemd. It's just a random binary. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl -- Baron Vladimir Harkonnen _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel