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). _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- [systemd-devel] isolate and socket activation Matthew Monaco
- Re: [systemd-devel] isolate and socket a... Zbigniew Jędrzejewski-Szmek