[Bug 531912] Re: /etc/init.d/ssh seems to work, but actually upstart is used.

[Rolf Leggewie]

Thanks to everyone involved in getting this fixed.  I'll say that I
still don't have much confidence in all of this, but judging by the test
case, it seems that at least for my lucid system there is no longer a
discrepancy between the status managed with init.d and upstart.  Please
release to -updates.

As a user I'm thankful for all the work the devs do.  I think it's quite
obvious from what Ubuntu has achieved that everybody involved is really
trying their best and it mostly works extremely well.  But I will not
hide the fact that I also feel that upstart was very hastily introduced
WAY before it's time.  Dapper vservers are still stuck without ANY
upgrade path AT ALL because of upstart.  I feel this is quite outrageous
given the promise of an LTS.  There isn't much live left for dapper
users and obviously, I'd much rather run lucid by now.  I hope bug
430224 will soon get fixed for lucid.

So, thanks again to the devs for their work.  Sometimes you can't win, I
guess ;-)

** Tags added: verification-done
** Tags removed: verification-needed

-- 
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/531912

Title:
  /etc/init.d/ssh seems to work, but actually upstart is used.

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