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

[Tokuko]

This issue has hit me multiple times now. I'm usually working on Solaris, HP-UX and AIX. All of these simply issue a big loud warning on the console, but try to continue to boot, which I guess is what most administrators (at least I) expect.
As the last entry was 3 years ago - has any decision been reached?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/583542

Title:
  ssh server doesn't start when irrelevant filesystems are not available

Status in “openssh” package in Ubuntu:
  Triaged

Bug description:
  In Lucid, the SSH daemon won't start at boot unless all filesystems
  listed in fstab can be mounted.  This is annoying to the administrator
  because some fstab entries are irrelevant and/or could be expected to
  have transient failures.  When SSH doesn't start, it's impossible for
  the admin to do an in-band fix of these filesystems.

  Examples of when filesystems might not mount:

  Underlying device not attached
  NFS server unavailable
  iSCSI target unavailable
  RAID without a quorum of member devices
  Kernel package upgrade disabled certain filesystem modules

  And so forth.  The line "start on filesystem" should probably be
  edited to something a bit more robust.

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