Public bug reported:
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.
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
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.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
