From owner-freebsd-sparc64@FreeBSD.ORG Thu Jun 24 09:00:46 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 291EA16A4CE for ; Thu, 24 Jun 2004 09:00:46 +0000 (GMT) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id D22A243D55 for ; Thu, 24 Jun 2004 09:00:45 +0000 (GMT) (envelope-from j@ida.interface-business.de) Received: by ida.interface-business.de (Postfix, from userid 107) id 894FB7A49; Thu, 24 Jun 2004 11:00:43 +0200 (MET DST) Date: Thu, 24 Jun 2004 11:00:43 +0200 From: Joerg Wunsch To: sparc64@freebsd.org Message-ID: <20040624110043.A30818@ida.interface-business.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Phone: +49-351-31809-14 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Organization: interface systems GmbH, Dresden cc: dhcp-hackers@isc.org Subject: Known 64-bit time_t issue with dhclient? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 09:00:46 -0000 # 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@interface-systems.de http://www.interface-systems.de/~j/