From owner-freebsd-questions@FreeBSD.ORG Mon Mar 22 15:40:50 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 A62E016A4D0 for ; Mon, 22 Mar 2004 15:40:50 -0800 (PST) Received: from mhultra.aero.org (mhultra.aero.org [130.221.88.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 020FC43D48 for ; Mon, 22 Mar 2004 15:40:50 -0800 (PST) (envelope-from cal@rushg.aero.org) Received: from rushe.aero.org ([130.221.24.10] [130.221.24.10]) by mhultra.aero.org with ESMTP for freebsd-questions@freebsd.org; Mon, 22 Mar 2004 15:38:21 -0800 Received: from calamari.aero.org (calamari.aero.org [130.221.26.26]) by rushe.aero.org (8.11.7p1+Sun/8.11.6) with ESMTP id i2MNcJf06151; Mon, 22 Mar 2004 15:38:20 -0800 (PST) From: Chris Landauer Received: (from cal@localhost) by calamari.aero.org (8.11.6/8.11.6) id i2MNewU01602; Mon, 22 Mar 2004 15:40:58 -0800 (PST) (envelope-from cal) Date: Mon, 22 Mar 2004 15:40:58 -0800 (PST) Message-Id: <200403222340.i2MNewU01602@calamari.aero.org> To: freebsd-questions@freebsd.org cc: cal@rush.aero.org Subject: 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: Mon, 22 Mar 2004 23:40:50 -0000 hihi, all - i am running some very long programs, and it appears that time wraps around in its counting (the 72 cpu hour program did not wrap, the 164 cpu hour program did) i am running 5.1 with the GENERIC kernel, and using /bin/csh with 'time ' (i also tried SuSe Linux 9.0, but i had to change away from it because it would crash the machine after some dozens of hours - but i normally run FreeBSD anyway, which has not crashed even for 3 cpu week runs) i found no hint about the maximum possible counted time in the manuals for any of the likely candidates 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) finally, can anybody tell me what the default tick size is? or better, where i can look to find out? more soon, cal Dr. Christopher Landauer Aerospace Integration Science Center The Aerospace Corporation cal@aero.org