Tomasz,
sockets.target is rather odd for me. If I had (hypothetical) socket-activable service, which is only relevant in GUI environment, I would like its socket to be pulled in by graphical.target. Using sockets.target would let my hypothetical service to be available in text-only boot.
Socket-activatable services are very useful across the board - for system and user level services running with and without a GUI as there is nothing GUI specific at all about them. And even if this hypothetical service was only useful in a GUI environment (for whatever reason), where would be the harm in having systemd register the socket in a non-GUI environment where presumable nothing would be trying to connect on the socket and thus nothing activates the service. -- Regards, Peter _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
