From owner-freebsd-current Wed Aug 19 23:02:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25578 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:02:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25569 for ; Wed, 19 Aug 1998 23:02:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id HAA00536; Thu, 20 Aug 1998 07:58:35 +0200 (CEST) To: Terry Lambert cc: green@unixhelp.org, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Thu, 20 Aug 1998 04:51:25 -0000." <199808200451.VAA13481@usr02.primenet.com> Date: Thu, 20 Aug 1998 07:58:34 +0200 Message-ID: <534.903592714@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808200451.VAA13481@usr02.primenet.com>, Terry Lambert writes: >> >> It's probably a good idea to get this fixed ASAP, since people have been >> >> complaining about this exact bug for months now. Would anyone like to give >> >> me any pointers to where to start evaluating the code at, or what >> >> functions this could be caused by? I think I'll check the process >> >> accounting code first then the actual timing code, if noone has any better >> >> ideas. >> > >> >My suggestion would be to implement this timing using a monoclock. >> >> I fully agree, great idea Terry! >> >> We've had that for several months already :-) > >Cool! Then we can mark this bug resolved! 8-). No, we can mark your diagnosis as wrong. :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message