Based on the description, I'm marking this bug invalid. You do *not*
have to have the network up before starting mountall, including with nfs
/ nfs4 mounts, whIch I'm doing here with no problems. You *do* have to
have your network configuration done in such a way that it doesn't block
waiting on mountall - so either it needs to be statically configured via
/etc/network/interfaces, or if you use NetworkManager, you need to use
system-level profiles and not user-level ones.
So I'm pretty sure the problem you ran into was a configuration error
rather than a bug in mountall. If you disagree, please provide more
information about your network config.
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598599
Title:
mountall needs dhclient to be running
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/598599/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
