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
** Changed in: openssh (Ubuntu)
Status: New = Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
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
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
This may be out of scope for a bug report, but why not change the way an
upstart job describes its start conditions? ssh, for example, could
supply a script which checks if /usr is mounted. The script(s) can be
run after every upstart job completes, and when all conditions are met
the new jobs
hm... now that i'm reading the man page you directed me at, the
nobootwait and optional flags do seem to solve this issue.
at very least, though, there is an educational problem here. I was
unaware of these options as I'm sure several sysadmins or users are.
--
ssh server doesn't start when
This is especially important for remotely controlled servers which have
no console access (e.g., Amazon EC2).
--
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
