Known 64-bit time_t issue with dhclient?

[Joerg Wunsch]

# dhclient -v hme0
Internet Software Consortium DHCP Client V3.0.1rc12
Copyright 1995-2002 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on BPF/hme0/08:00:20:fe:a2:70
Sending on   BPF/hme0/08:00:20:fe:a2:70
Sending on   Socket/fallback
DHCPDISCOVER on hme0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 193.101.57.34
DHCPREQUEST on hme0 to 255.255.255.255 port 67
DHCPACK from 193.101.57.34
bound to 193.101.57.69 -- renewal in 4673210995445900712 seconds.
                                     ^^^^^^^^^^^^^^^^^^^

Perhaps that's only an artefact of the way it is printed (I see a cast
to `long' there, which is a shorter data type than the actual
expression when running on a 64-bit time_t host).  However, dhclient
internally completely relies on 32-bit times it seems.  Also, I'm not
sure whether it's related, but I see a fairly hectic and never ending
DHCP traffic on the wire, despite of the fact the lease negotiation
has been reported to be OK above.  This eats up a good bit of machine
power, and can only be stopped by killing dhclient away.

Is anybody successfully using dhclient on a 64-bit time_t machine
without these symptoms?

-- 
J"org Wunsch					       Unix support engineer
joerg_wunsch at interface-systems.de        http://www.interface-systems.de/~j/