Problem with DHCLIENT vs 64-bit time_t
Garance A Drosihn
drosih at rpi.edu
Sat Feb 21 23:59:28 PST 2004
At 8:33 PM -0500 2/16/04, Garance A Drosihn wrote:
>At 5:13 PM -0600 2/15/04, matt wrote:
>And in a later message, he wrote:
>> Killing dhclient brought things back to normal - and yes, I
>> did remove /var/db/dhcp.leases (had to, dhclient wouldn't
>> work until I did). My kernel was just a run of the mill
>> GENERIC, no changes.
>Well, there does seem to be some kind of problem here, but I
>don't know what to do about it just yet. In my earlier testing,
>I did do some testing with a dhcp-configured machine, but not a
>lot of it.
I did a little more testing on this. On my 32-bTT sparc64 system,
I can run 'dhclient -v hme0' by hand (after the system has
booted up), and it works fine. On the same system upgraded to
64-bTT, the command hangs after printing out
'Sending on Socket/fallback'
I let it sit there for several minutes, and it just never got
past that point. I had to attention out of it.
I did find that if I install the port for net/isc-dhcp3-client,
I can type:
and it seems to work fine. (the version in the ports-collection
does not support a -v option). The only obviously incorrect
comment in the output from the program was:
bound to 188.8.131.52 -- renewal in 4627546198780150248 seconds.
I am pretty sure that our lease-renewal time is somewhat smaller
So, there definitely is something wrong with the dhclient from
the base system But it might be that people having trouble with
dhcp on 64-bTT sparc systems could use the port, at least for
disclaimer: I just ran the port-built version by hand. I did
not check to see how you would run this version instead of the
base-system version at system-startup.
Garance Alistair Drosehn = gad at gilead.netel.rpi.edu
Senior Systems Programmer or gad at freebsd.org
Rensselaer Polytechnic Institute or drosih at rpi.edu
More information about the freebsd-sparc64