[systemd-devel] isolate and socket activation

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Fri Mar 22 12:49:40 PDT 2013

On Fri, Mar 22, 2013 at 07:50:43AM -0600, Matthew Monaco wrote:
> I noticed that when isolating a target that requires a <unit>.socket, the
> <unit>.service which the socket activates will be stopped. Is this intentional?
> I expected the service to be left alone (even in the weaker case that the socket
> wasn't already active).
Quoting "systemdctl(1)":

isolate NAME
           Start the unit specified on the command line and its dependencies and stop all others.

If <unit>.service is not a dependency of the isolated target, it will be stopped.


More information about the systemd-devel mailing list