** Description changed: Binary package hint: upstart - If one has /var (or /var/lib or /var/lib/nfs for that matter) on it's - own filesystem the statd.conf start races with the mounting of /var as + If one has /var (or /var/lib or /var/lib/nfs for that matter) on its own + filesystem the statd.conf start races with the mounting of /var as rpc.statd needs /var/lib/nfs to be available in order to work. I am sure this is not the only occurrence of this type of problem. A knee-jerk solution is to simply spin in statd.conf waiting for /var/lib/nfs to be available, but polling sucks, especially for something like upstart who's whole purpose is to be an event driven action manager.
** Description changed: Binary package hint: upstart If one has /var (or /var/lib or /var/lib/nfs for that matter) on its own filesystem the statd.conf start races with the mounting of /var as rpc.statd needs /var/lib/nfs to be available in order to work. I am sure this is not the only occurrence of this type of problem. A knee-jerk solution is to simply spin in statd.conf waiting for /var/lib/nfs to be available, but polling sucks, especially for - something like upstart who's whole purpose is to be an event driven + something like upstart whose whole purpose is to be an event driven action manager. -- mountall for /var races with rpc.statd https://bugs.launchpad.net/bugs/525154 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
