Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-10 Thread David Timothy Strauss
On Tue, Sep 8, 2015 at 10:48 AM Simon McVittie < simon.mcvit...@collabora.co.uk> wrote: > As far as I understand it, this duplication is present to give the > sysadmin a choice between two ways to run sshd, depending on this > particular ssh server's requirements. > > If ssh access is frequently u

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-09 Thread Francis Moreau
On 09/08/2015 07:48 PM, Simon McVittie wrote: > On 08/09/15 13:55, Francis Moreau wrote: >> On 09/08/2015 12:09 PM, Richard Maw wrote: >>> I understood that the common configuration for socket activated sshd was to >>> have a sshd.service for if you want it to always be running, and a pair of >>> s

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-08 Thread Simon McVittie
On 08/09/15 13:55, Francis Moreau wrote: > On 09/08/2015 12:09 PM, Richard Maw wrote: >> I understood that the common configuration for socket activated sshd was to >> have a sshd.service for if you want it to always be running, and a pair of >> sshd@.service and sshd.socket. > > Ah no, with this

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-08 Thread Francis Moreau
On 09/08/2015 12:09 PM, Richard Maw wrote: > On Tue, Sep 08, 2015 at 10:05:05AM +0200, Francis Moreau wrote: >> On 09/07/2015 11:28 AM, Richard Maw wrote: >>> On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote: How is this handled ? Should we put a big warning in sshd_config to hin

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-08 Thread Richard Maw
On Tue, Sep 08, 2015 at 10:05:05AM +0200, Francis Moreau wrote: > On 09/07/2015 11:28 AM, Richard Maw wrote: > > On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote: > >> How is this handled ? Should we put a big warning in sshd_config to hint > >> user to configure ListenAddress in sshd

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-08 Thread Francis Moreau
On 09/07/2015 11:28 AM, Richard Maw wrote: > On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote: >> 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

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-07 Thread Richard Maw
On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote: > 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 ss

[systemd-devel] Possible confusion with socket activation and daemon own configuration

2015-09-06 Thread Francis Moreau
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