** Tags added: regression-release
--
service ssh restart does not test the configuration file
https://bugs.launchpad.net/bugs/624361
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Further information, this was introduced in 10.04. 9.10 and prior still
used the init.d script.
--
service ssh restart does not test the configuration file
https://bugs.launchpad.net/bugs/624361
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hi Simon, thanks very much for filing this bug report and working with
us to make Ubuntu better.
Because of the way upstart and sshd work together, its hard to detect
failures. The reason try-restart worked was that it falls through in
/usr/sbin/service, as its not one of the regular actions that
Hi Clint,
Thanks for your additional input. Regarding your suggestion to add a
pre-stop action that runs sshd -t I have to disagree. When I call
service ssh stop I expect the daemon to quit even if there are
configuration errors.
I am not familiar with upstart but maybe there are some hooks
I see your point Simon, and I agree thats what I expect too. I think a
case can be made that sometimes failing safe means doing something
non-intuitive, though in doing something like that, there has to be a
good reason.
There is no pre-restart stanza, and upon looking at upstart's code, it
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/624361/+attachment/1519330/+files/Dependencies.txt
--
service ssh restart does not test the configuration file
https://bugs.launchpad.net/bugs/624361
You received this bug notification because you are a member of Ubuntu
I just found this in OpenSSH changelog for Maverick :
openssh (1:5.5p1-3ubuntu1) maverick; urgency=low
...
- Convert to Upstart. The init script is still here for the benefit of
people running sshd in chroots.
...
Is it planned to drop the init script eventually ?
--
service ssh
