Date: Tue, 16 Jun 1998 23:42:34 +0100 From: James Raynard <fcurrent@jraynard.demon.co.uk> To: Chris Timmons <skynyrd@opus.cts.cwu.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Cputime limit exceeded Message-ID: <19980616234234.57585@jraynard.demon.co.uk> In-Reply-To: <Pine.BSF.3.96.980616143542.9333H-100000@opus.cts.cwu.edu>; from Chris Timmons on Tue, Jun 16, 1998 at 02:36:51PM -0700 References: <19980615223958.33510@jraynard.demon.co.uk> <Pine.BSF.3.96.980616143542.9333H-100000@opus.cts.cwu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 16, 1998 at 02:36:51PM -0700, Chris Timmons wrote: > On Mon, 15 Jun 1998, James Raynard wrote: > > > 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. > > 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 a week or two ago in which bde said it was something to do with different values being used for "infinity" in different places. Having been away from -current for a week, I was hoping there might be a fix available by now. James 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?19980616234234.57585>