Date: Tue, 23 Mar 2004 12:41:47 -0800 From: Chris Pressey <cpressey@catseye.mine.nu> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: wraparound value for time 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 23 Mar 2004 17:38:02 +0000 Matthew Seaman <m.seaman@infracaninophile.co.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040323124147.6ef9e92d.cpressey>