Hello, Usually it's possible to specify the listen address a daemon/service will listen to. For example, sshd has the 'ListenAddress' option that can be used in its config file (sshd_config) which specifies the local addresses sshd(8) should listen on.
The same parameter should be defined also in sshd.socket if we want to use socket activation for sshd. This can lead to odd situations because some listening addresses can be defined in sshd_config whereas they're not specified in sshd.socket unit file. In this case this address will never wake up sshd. However if sshd is already running, because another listening address is used, then it will serve the address only defined in sshd_config. I think it's confusing (but I may be missing something). How is this handled ? Should we put a big warning in sshd_config to hint user to configure ListenAddress in sshd.socket in the case socket activation is used ? Or should sshd simply ignore all listening addresses defined in sshd_config when in socket activation mode ? Thanks. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel