From owner-freebsd-questions@FreeBSD.ORG Tue Mar 23 12:36:08 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B12416A4CE for ; Tue, 23 Mar 2004 12:36:08 -0800 (PST) Received: from priv-edtnes12-hme0.telusplanet.net (outbound03.telus.net [199.185.220.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id D460D43D49 for ; Tue, 23 Mar 2004 12:36:07 -0800 (PST) (envelope-from cpressey@catseye.mine.nu) Received: from catseye.biscuit.boo ([154.5.85.228]) by priv-edtnes12-hme0.telusplanet.netSMTP <20040323203607.ISMU23321.priv-edtnes12-hme0.telusplanet.net@catseye.biscuit.boo>; Tue, 23 Mar 2004 13:36:07 -0700 Date: Tue, 23 Mar 2004 12:41:47 -0800 From: Chris Pressey To: Matthew Seaman Message-Id: <20040323124147.6ef9e92d.cpressey@catseye.mine.nu> In-Reply-To: <20040323173802.GC973@happy-idiot-talk.infracaninophile.co.uk> References: <200403222340.i2MNewU01602@calamari.aero.org> <20040323173802.GC973@happy-idiot-talk.infracaninophile.co.uk> Organization: Cat's Eye Technologies X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: cal@rushg.aero.org cc: freebsd-questions@freebsd.org Subject: Re: wraparound value for time X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2004 20:36:08 -0000 On Tue, 23 Mar 2004 17:38:02 +0000 Matthew Seaman wrote: > On Mon, Mar 22, 2004 at 03:40:58PM -0800, Chris Landauer wrote: > > > i tried to figure out where the actual code for time is, but i can't > > quite tell - it appears to be buried inside csh somewhere (it also > > appears that there are several different possibilities for the data > > type used, depending on some compile time parameters for the csh > > compilation) > > There's also a standalone time(1) command which does much the same as > the shell built-in 'time' but has completely different internals. > [...] > With any luck the internal representation will be different and so the > supported range of values may be larger. Yep, I just checked the source, and time(1) does use struct timeval's internally. Should be sufficient to time something running for several decades. -Chris