Comment 3 for bug 583542

> 'filesystem' is documented as being appropriate for most normal
> services, so surely many other services have the same problem? Most
> notably, rc-sysinit starts on filesystem, so you'll never reach runlevel
> 2 if that event is never emitted. It seems to me that any change I
> might make in ssh would tend to make matters worse, not better.

I agree that this is likely to affect other services or jobs also. I'm
not aware of any event that would be better.

That said, this is a real issue, the 'nobootwait' may be a suitable
workaround for lucid, but there needs to be some way of starting services
that is reliable. All sorts of things could result in a /etc/fstab that
wasn't perfect (failed disk, '/dev/sdXX' entry rather than UUID= and
changed kernel, ...) . Having ssh not start means a physical touch to the
machine or out of band interface has to be used to service it. In
EC2/UEC, there *is* no out of band interface, or physical touch.