[systemd-devel] isolate and socket activation

Matthew Monaco matt at 0x01b.net
Fri Mar 22 06:50:43 PDT 2013

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).

More information about the systemd-devel mailing list