(if this is wrong, then please provide steps to reproduce on a current
Ubuntu release and reopen)
** Changed in: openssh (Ubuntu)
Status: New => Fix Released
** Changed in: lsb (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
I can't reproduce this on Eoan, so I believe this problem is fixed. In
particular, since the init.d handling was overhauled when systemd was
introduced, it is likely that the code responsible has completely
changed and this bug no longer exists. I'm marking as Fix Released
accordingly.
--
You rec
Did you check for the existence of the /run/sshd directory? Is
UsePrivilegeSeparation set to yes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458476
Title:
/etc/init.d/ssh gives OK status even if
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458476
Title:
/etc/init.d/ssh gives OK status even if daemon fails to launch
To mana
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458476
Title:
/etc/init.d/ssh gives OK status even if daemon fails to laun
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34159616/Dependencies.txt
--
/etc/init.d/ssh gives OK status even if daemon fails to launch
https://bugs.launchpad.net/bugs/458476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
