Thanx Steve for feedback.
Yes, I do have a separate /var partition (LVM). So I guess all I achieved with 
the "networking" condition is to add enough delay so that /var is mounted when 
statd starts. Actually, I can confirm the fsck for this /var partition always 
comes after the "statd main process ended" errors. So I guess it makes this bug 
a duplicate of the other /var related bugs.
OT: can you point me to the way to enable debug/verbosity in the upstart 
process? I search for that feature a lot, to no avail.

-- 
"init: statd main process ended, respawning" upstart problem
https://bugs.launchpad.net/bugs/568082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to