From owner-freebsd-questions@FreeBSD.ORG Tue Mar 23 09:28:36 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 30FB416A4CE for ; Tue, 23 Mar 2004 09:28:36 -0800 (PST) Received: from mhultra.aero.org (mhultra.aero.org [130.221.88.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B06943D55 for ; Tue, 23 Mar 2004 09:28:36 -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; Tue, 23 Mar 2004 09:27:18 -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 i2NHRHf19222; Tue, 23 Mar 2004 09:27:17 -0800 (PST) From: Chris Landauer Received: (from cal@localhost) by calamari.aero.org (8.11.6/8.11.6) id i2NHU0r09531; Tue, 23 Mar 2004 09:30:00 -0800 (PST) (envelope-from cal) Date: Tue, 23 Mar 2004 09:30:00 -0800 (PST) Message-Id: <200403231730.i2NHU0r09531@calamari.aero.org> To: dan@dan.emsphone.com cc: freebsd-questions@freebsd.org cc: cal@rush.aero.org Subject: Re: wraparound value for (user) 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 17:28:36 -0000 hihi, dan - you werote: > Which value wrapped? user, system, or elapsed? > The best I could come up with was that elapsed time might be stored in > a long variable in milliseconds, which would wrap at 49.7 days. User > and system times are stored as "struct timeval"s and should never wrap. thanx for answering so quickly - it is the user cpu time that wraps, in much less than 49 days, apparently (elapsed time was 164 hrs and 340 hrs in the two cases that wrapped, and the cpu percentage should have been between 90 and 95) i did finally find struct timeval, which has a long - arithmetically, i convinced myself that the value had to be not an unsigned one (so the wrapped values were negative, but printed as positive), but i need to look further at the resolution issue - i will study it further and report the results as soon as i have something definitive (or at least useful) to say more later, cal Chris Landauer Aerospace Integration Science Center cal@aero.org