[Bug 583542] Re: ssh server doesn't start when irrelevant filesystems are not available

[Colin Watson]

I don't believe mountall emits any event that would be suitable for
this.  The only other plausible one is local-filesystems, whose manual
page notes that it may well not cover /usr so it's not suitable for use
by the ssh job.

'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.

Can't you use the nobootwait option in /etc/fstab to avoid holding up
boot for filesystems that aren't needed to get up and running?  This is
documented in fstab(5).

-- 
ssh server doesn't start when irrelevant filesystems are not available
https://bugs.launchpad.net/bugs/583542
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.