From owner-freebsd-current Tue Jun 16 23:49:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20173 for freebsd-current-outgoing; Tue, 16 Jun 1998 23:49:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20150 for ; Tue, 16 Jun 1998 23:49:11 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA09080; Wed, 17 Jun 1998 16:49:02 +1000 Date: Wed, 17 Jun 1998 16:49:02 +1000 From: Bruce Evans Message-Id: <199806170649.QAA09080@godzilla.zeta.org.au> To: fcurrent@jraynard.demon.co.uk, skynyrd@opus.cts.cwu.edu Subject: Re: Cputime limit exceeded Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Anyone have a fix for the above? It seems to happen just after >> > a "calcru: negative time of -xxxxxxxx usec for pid yyy (zzzz)" >> > error. Negative times are now interpreted as huge positive times (of about 580000 years). Negative times can't happen :-). >> Hmmm.... make sure you know what login class the processes being killed >> belong to (see limits(1)) and then hack /etc/login.conf to be more >> friendly to them. > >No, they run as root which has unlimited cputime (that was the first thing >I checked!). The reason why I posted was that I remembered some discussion Root actually has a limit of only about 290 thousand years. It used to be about 290 billion years, but conversion from seconds to microseconds now reduces its range by a factor of 10^6. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message