> I do think there's still a bit of a bug here in mountall. Granted,
> there was something wrong (most recently missing conffiles)
> that caused a failure. But, mountall failed in a pretty bad way:
Well, it failed in a bad way because large chunks of its brain were
missing. I don't think we're going to make the mountall code more
complex to support the case of core upstart jobs being absent from the
filesystem.
> Seems like we could do better than that, even booting in to a crippled
> environment like I did by hacking the 90s in instead of
> NIH_DBUS_TIMEOUT_NEVER would be vastly superior to what we've got at the
> moment.
No, there's no fixed timeout that's appropriate here. If a user wants
to run a job at boot after mounting one of their filesystems, and that
job takes 5 minutes to complete, that's perfectly valid.
** Changed in: mountall (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839166
Title:
mountall hangs while trying to send dbus? messages for /proc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/839166/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
