Date: Wed, 19 Aug 1998 17:22:50 -0400 (EDT) From: Brian Feldman <green@unixhelp.org> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? Message-ID: <Pine.BSF.4.02.9808191720490.29282-100000@zone.syracuse.net> In-Reply-To: <199808191930.FAA23515@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Brian Feldman green@unixhelp.org On Thu, 20 Aug 1998, Bruce Evans wrote: > > I found this on a 3 month old snap, and have now replicated it > >on 3.0-980818-SNAP. > > > >for i in /bin/*; do > > time rsh nodename uptime > >done > > > > Yields the following output: > > > >..... > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > 0.19s real 0.00s user 0.00s system > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > 0.20s real 33554431.00s user 0.00s system > > This is probably just a symptom of a negative times bug and assorted > overflows. This negative times bug usually kills processes with a > SIGXCPU. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02.9808191720490.29282-100000>