Hi Steve, the server is now being used with a very dirty workaround I've written:
crontab -e @reboot /usr/bin/my-mount-script.sh the script is really stupid, it just keep trying mount -a every 5 seconds until it found a file .checked that is present in the root directory of the NFS sharing. and the first time it try it always get the statd error. This is to say that I can't test on that server anymore. If you can wait I'll be able to do tests after 22/02/2012 when this server will be taken off-line. but I doubt that second try is performed by the bootup.. it's more like it's the log from my cron script trying. I don't know the bootup process in details and what does print that message, but the common meaning of "Name or service not known" is DNS failure, which doesn't make sense on an IP address. anyway I'm not alone: http://ubuntuforums.org/showthread.php?t=1699331 do you know of anyway of making the networks logs be more verbose without upgrading the server? I'm fine modifying the bootup scripts if you give me precise instructions thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933575 Title: NFS not being mounted at boot time - rpc.statd is not running but is required for remote locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/933575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
