[Bug 801123] Re: sshd init script does not use the option "--pidfile"

Scott Moser smoser at canonical.com
Thu Jun 23 19:15:25 UTC 2011


> So again, the option --pidfile is not used in the init script,
>  because it's value gets overwritten by sshd_config settings.

Well, its not really "overwritten", --pidfile to 'start-stop-daemon' is
not intending to influence sshd's behavior.  As discussed in bug 277120
that you referenced, It is only used to determine if there is a process
already running or not (and avoid starting again).

The value of --pidfile as given to 'start-stop-daemon' must be the same
as defined in sshd_config (or, the default value of PidFile).

> It should get the right value from the config file, which is defined in 
> /etc/default/ssh-<whatever> in a perfect world.

I'm confused what '<whatever>' would be.  The existing /etc/init.d/ssh
script in lucid reads '/etc/default/ssh', not 'ssh-<something>'.  Were
you hoping to have 1 definitive location for this setting?  It seems
like to do that you'd have to either invoke sshd with '-o PidFile=' or
scrape it from the sshd config file.

Finally, 10.04 was the last release with /etc/init.d/ssh, it was subsequently replaced by an upstart job in /etc/init/ssh.conf.
I'm interested to see if you believe your use case is better handled there.   See the default ssh.conf file at
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/openssh/oneiric/view/head:/debian/openssh-server.ssh.upstart



** Changed in: openssh (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/801123

Title:
  sshd init script does not use the option "--pidfile"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/801123/+subscriptions



More information about the Ubuntu-server-bugs mailing list