It seems to me that it happens with my desktop too. I have 2 ubuntu servers 10.04 and one desktop 10.04. And statd problem exists only on desktop itself, servers go fine.
As a simple comparison I see the difference in network interfaces: servers has a static interface config, while desktop has network-manager config, thus network interfaces on desktop are unconfigured until desktop login and there is nowhere to do `sm-notify` nfs cliens about reeboot. So sm-notify respawns in awaiting them to be ready for action, but killed because respawning to fast. This is only a supposition... -- statd does not start automatically when needed nor can be forced to start on boot https://bugs.launchpad.net/bugs/581941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
