From owner-freebsd-current Tue Jun 16 12:00:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01669 for freebsd-current-outgoing; Tue, 16 Jun 1998 12:00:31 -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 MAA01644 for ; Tue, 16 Jun 1998 12:00:04 -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 WAA00972; Mon, 15 Jun 1998 22:39:59 +0100 (BST) (envelope-from fcurrent) Message-ID: <19980615223958.33510@jraynard.demon.co.uk> Date: Mon, 15 Jun 1998 22:39:58 +0100 From: James Raynard To: freebsd-current@FreeBSD.ORG Subject: Cputime limit exceeded Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e 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. (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