Package: nfs-common Version: 1:1.1.1~git-20070929-1 Summary:
nfs-common will have rpc.statd start itself before the networking subsystem. If this is done rpc.statd will not register and therefore preventing the use of automount to work after bootup. If you restart nfs-common after bootup automount will then work. The solution to this is to move nfs-common init script to start at a later time after networking. I'm surprised no one had reported this before. Details: rpc.statd will fail upon bootup with: Nov 24 16:12:59 (none) rpc.statd[2284]: Version 1.1.0 Starting Nov 24 16:12:59 (none) rpc.statd[2284]: unable to register (statd, 1 udp). This prevents automount from working. This is cause because of the order of init scripts: lrwxrwxrwx 1 root root 20 Sep 18 12:13 S20nfs-common -> ../init.d/nfs-common lrwxr-xr-x 1 root root 20 Aug 23 2004 S35networking -> ../init.d/networking Moving S20nfs-common to something above S35 will correct this. I've set it to S40 and this resolves it. Luis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
