From owner-freebsd-questions  Fri Sep 25 08:07:39 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA13918
          for freebsd-questions-outgoing; Fri, 25 Sep 1998 08:07:39 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13913;
          Fri, 25 Sep 1998 08:07:36 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA24807;
	Fri, 25 Sep 1998 08:08:23 -0700 (PDT)
Message-Id: <199809251508.IAA24807@implode.root.com>
To: Nicole <freelist@webweaver.net>
cc: freebsd-isp@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG
Subject: Re: PID killed, exceeeded maximum CPU limit... 
In-reply-to: Your message of "Fri, 25 Sep 1998 05:01:24 PDT."
             <XFMail.980925050124.freelist@webweaver.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 25 Sep 1998 08:08:22 -0700
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Please forgive the Niaveness of this question, and my poor spelling at 5:50 in
>the morning, but what usually causes something to exceed the CPU limit and what
>CPU limit is the message below probobly refering too. How can I prevent this?
>
>
>Sep 25 04:45:00 test2 /kernel: pid 137 (inetd), uid 0, was killed: exceeded
>maximum CPU limit

   ...a bug in the FreeBSD clock/accounting code that causes it to come up
with negative numbers sometimes. I believe this has been fixed - what are
you running on the machine?

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message