From owner-freebsd-current Tue Jun 16 15:43:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10967 for freebsd-current-outgoing; Tue, 16 Jun 1998 15:43:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jraynard.demon.co.uk (jraynard.demon.co.uk [158.152.42.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10934 for ; Tue, 16 Jun 1998 15:43:30 -0700 (PDT) (envelope-from fcurrent@jraynard.demon.co.uk) Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.8.8/8.8.8) id XAA02911; Tue, 16 Jun 1998 23:42:34 +0100 (BST) (envelope-from fcurrent) Message-ID: <19980616234234.57585@jraynard.demon.co.uk> Date: Tue, 16 Jun 1998 23:42:34 +0100 From: James Raynard To: Chris Timmons Cc: freebsd-current@FreeBSD.ORG Subject: Re: Cputime limit exceeded References: <19980615223958.33510@jraynard.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Chris Timmons on Tue, Jun 16, 1998 at 02:36:51PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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