Comment 2 for bug 470776
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
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