Comment 2 for bug 776407

mahmood, thanks for the bug report!

This looks like the expected sequence, as portmap-wait will be killed once portmap has started, and statd-mounting will be killed once statd has "started". However, it looks like the statd job uses 'expect fork' to time its 'started' event. Since it also uses a script, this means as soon as the script has started running the started event is likely emitted, and the waiting mountall is allowed to go forward with the mount. I wonder if we don't need to switch to 'expect daemon', or use a post-start to watch for the daemon to be fully running.

Can you run 'apport-collect 776407' on this system to give us more information? Also it would be helpful if apport-collect doesn't add it, to attach a copy of /etc/fstab

Thank you!