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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/458476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
