[FIX] Was: Re: [Voyage-linux] [BUG REPORT] voyage-0.2pre4: DHCP client could not write to /var/run/

[Leon Woestenberg]

Hello all,

sorry to bother you all again with my ramblings. I think I found a 
proper fix for the bug I described earlier.

Leon Woestenberg wrote:
> Hello,
>
> I wanted to report a bug that I have found during my PXE/NFS tests (on 
> WRAP.2C using voyage-0.2pre4 on CF disk).
>
> The DHCP client does not seem to have write access to "/var/run" when 
> is gets its lease. Consequently, there is not PID or leases file in 
> this directory.
Well, the DHCP client *did have* write access, but the bootclean() call 
in mountnfs.sh (from rcS.d/S45nfsmount.sh) cleans the /var/run directory 
right after DHCP wrote to it. That causes the DHCP daemon to 
(temporarely) bring eth0 down --- fatal for a NFS root mount over eth0.

See my logging below to show the problem.

The solution is to remove , or comment out the last line in 
/etc/init.d/mountnfs.sh:

#
#       Clean /tmp, /var/lock, /var/run
#
#bootclean mountnfs

Googling for "bootclean mountnfs.sh" shows similar problems and similar 
solutions.

At least for root NFS mounts on Voyage, this fix is needed.

Regards,

Leon.


---
eth0: link up.
<...>
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 10.1.0.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.1.0.1
bound to 10.1.0.105 -- renewal in 300 seconds.
done.
----bootclean called by mountnfs ----
Cleaning /tmp /var/runremoved `./dhclient.eth0.pid'
removed `./dhclient.eth0.leases'
 /var/lock.
---