From owner-freebsd-current Tue Jun 16 14:37:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28899 for freebsd-current-outgoing; Tue, 16 Jun 1998 14:37:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28893 for ; Tue, 16 Jun 1998 14:37:05 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id OAA13698; Tue, 16 Jun 1998 14:36:51 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Tue, 16 Jun 1998 14:36:51 -0700 (PDT) From: Chris Timmons To: James Raynard cc: freebsd-current@FreeBSD.ORG Subject: Re: Cputime limit exceeded In-Reply-To: <19980615223958.33510@jraynard.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -Chris 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. > > (Apologies if this has mentioned before, but I've just read the last > week's worth of -current and didn't see anything obvious). > > James (having lots of problems with ctm processes getting killed) > > > 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