OK, if /etc/init/ssh doesn't fully replicate the functionality of the /etc/init.d/ssh script to include properly setting up chrooted environments and properly handling libc6 updates then what benefit does it provide users? Why, if you can't get Upstart to provide the same functionality as the /etc/init.d startup script, move control of sshd over to Upstart anyways? Again, what does it do for the users?
At least the fix for this bit of Upstart badness is easy enough, just remove /etc/init/ssh and start sshd with the script in init.d. Perhaps it's not as architecturally elegant as Upstart is supposed to be, but at least we all know that it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/531912 Title: /etc/init.d/ssh seems to work, but actually upstart is used. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
