Ubuntu
sysvinit package

  1. Bug #46516
  2. Comment #12

Comment 12 for bug 46516

Revision history for this message
Siegfried (siegzeit) wrote :

I've spent many hours getting around this problem in Dapper. None of the workarounds in the bug comments have worked for me. Finally I arrived across a solution that worked reliably:

Add the mountnfs command manually to the init script for the first program that requires NFS for me. In this case it's backuppc.

sudo sed -i '/"Starting $NAME..."/s@"Starting $NAME..."@&\n\t/etc/network/if-up.d/mountnfs@' /etc/init.d/backuppc

Next I made sure nfs-common started earlier than S20backuppc so that idmapd is started for successful mounting of the nfs4 directory.

sudo mv /etc/rc2.d/S21nfs-common /etc/rc2.d/S19nfs-common

It's a shame Ubuntu has such major problems with nfs4 that they aren't even mounted on boot when they're in the fstab file. The system that was setup depends on NFS being available, even for start up services, so a bug like this is unacceptable.