On Sat, Nov 24, 2007 at 07:37:57PM -0500, Luis R. Rodriguez wrote:
> 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.
Well, unsurprisingly this is because it seems to work for most other people,
including myself. :-)
> 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
What directory is this in? Certainly not in rcS.d, at least, which is what
matters at system startup:
fugl:/etc/rcS.d> ls -l *{networking,nfs-common}
lrwxrwxrwx 1 root root 20 2006-08-02 20:43 S40networking ->
../init.d/networking
lrwxrwxrwx 1 root root 20 2007-07-16 18:12 S44nfs-common ->
../init.d/nfs-common
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
