Your assumption is, I think, correct. When SIGUSR1 is received, it
tries to bring up the mount but fails because the parent mount isn't yet
ready. When it brings up the parent, it hasn't remembered that it can
bring up the network mount, so waits for SIGUSR1 again
** Summary changed:
- karmic: nfs shares not mounted on boot with ro-root
+ retry remote devices when parent is ready after SIGURS1
** Summary changed:
- retry remote devices when parent is ready after SIGURS1
+ retry remote devices when parent is ready after SIGUSR1
** Changed in: mountall (Ubuntu)
Status: New => Triaged
** Changed in: mountall (Ubuntu)
Importance: Undecided => Medium
--
retry remote devices when parent is ready after SIGUSR1
https://bugs.launchpad.net/bugs/470776
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
