On Monday 23 June 2003 15:39, poeml@cmdline.net wrote:
On Sat, Jun 21, 2003 at 01:24:28AM +0100, Dylan wrote:
for 'internal' services (NIS, nfs, ...). Now, two machines report during boot that DHCP for eth0 has failed, but by the time I can log in ifconfig reports a valid IP address. Also, if I manually rcnetwork restart, eth0 reports DHCP failure, but an immediate ifconfig shows an address. [...]
So, can anyone suggest what might be causing this behaviour? The router provides infinite leases (at least, theoretically) so I'd like to be able to
The infinity of the leases is causing this. The DHCP client immediately realizes that there is nothing to do (because the lease never ends) and quits, which is interpreted by the init script as failure.
OK, that makes sense.
It is a cosmetical problem (at least, unless you rely on the output or return code of the rcnetwork script for other purposes).
Would that be why the _net_dev option for nfs is causing problems on the offending machines?
It is on my todo list for the next SuSE version, but to my understanding it should not be a common situation because infinite leases should be a fairly uncommon configuration.
I suggest to change the lease duration to one week, or so, to work around the current limitation.
Unfortunately I don't have that control over the router (not a configurable option) so I'll put up with it. OTOH, is there a command I can add to the stop part of the rcnetwork script to explicitly release the lease? Cheers Dylan -- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg