Your message dated Sun, 25 Nov 2007 10:53:21 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#452758: nfs-common statd not registering - prevents
automount from working
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On Sat, Nov 24, 2007 at 08:48:21PM -0500, Luis R. Rodriguez wrote:
> Oh ok, I checked and I see now these scripts in rcS:
>
> [EMAIL PROTECTED]:~# ls -l /etc/rcS.d/*{networking,nfs-common}
> lrwxr-xr-x 1 root root 20 Aug 23 2004 /etc/rcS.d/K65networking ->
> ../init.d/networking
> lrwxrwxrwx 1 root root 20 Sep 18 12:13 /etc/rcS.d/S44nfs-common ->
> ../init.d/nfs-common
So your networking symlink is broken. Fix it and your system should be back
to normal. IOW, this is not a bug in nfs-utils -- closing. :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
