Comment 7 for bug 610863
Revision history for this message
| Andrew Edmunds (andrew-edmunds) wrote Re: mountall races with statd startup | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Theory A:
A "mounting TYPE=nfs" event while statd is stopped will cause statd to be started and mountall will block untill statd is running. However a "mounting TYPE=nfs" event while statd is in (say) pre-start or spawned state is ignored and does not block mountall. Therefore it is not guaranteed that statd is in running state when mountall calls mount.nfs.
Theory B:
statd is not really ready for business when upstart marks it as "runnning". It needs a post-start script that waits while it does initialization tasks such as registering with portmap.
I have not so far dug into the source sufficiently to prove or rule out either of these.
The log that I posted seems to support theory B but I have other examples that seem more consistent with theory A.