I also discovered the problem with 12.04 where exportfs fails at boot. In the log /var/log/boot.log I had errors for each client name e.g. "exportfs: Failed to resolve clientname
Search I found there are a number of trivial workarounds. - Adding the names to /etc/hosts. - Using IP numbers in the configurations. - Restarting nfs-server.service after bootup. I took a different route and checked out the script /etc/init.d/nfs- kernel-server. I have now added a sleep at the beginning to delay the NFS start long enough to allow the LAN and name resolution to come up - it seems to work. The first 3 dozen lines are below #!/bin/bash ### BEGIN INIT INFO # Provides: nfs-kernel-server # Required-Start: $remote_fs nfs-common $portmap $time # Required-Stop: $remote_fs nfs-common $portmap $time # Should-Start: $named # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Kernel NFS server support # Description: NFS is a popular protocol for file sharing across # TCP/IP networks. This service provides NFS server # functionality, which is configured via the # /etc/exports file. ### END INIT INFO # What is this? DESC="NFS kernel daemon" PREFIX=/usr # Mod by Richard Prior # Add delay on start to allow network and Name resolution services to be available # Without delay the exportfs will fail resolving machine names # Failures are listed in the /var/log/boot.log and look like # exportfs: Failed to resolve owl sleep 10 # Exit if required binaries are missing. [ -x $PREFIX/sbin/rpc.nfsd ] || exit 0 [ -x $PREFIX/sbin/rpc.mountd ] || exit 0 [ -x $PREFIX/sbin/exportfs ] || exit 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/848823 Title: nfs-kernel-server requires a real interface to be up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/848823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
