From owner-freebsd-isp Fri Sep 25 10:39:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07416 for freebsd-isp-outgoing; Fri, 25 Sep 1998 10:39:37 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07410 for ; Fri, 25 Sep 1998 10:39:35 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id MAA05731; Fri, 25 Sep 1998 12:39:37 -0500 (CDT) Received: from harkol-12.isdn.mke.execpc.com(169.207.64.140) by peak.mountin.net via smap (V1.3) id sma005729; Fri Sep 25 12:39:33 1998 Message-Id: <3.0.3.32.19980925123826.006e1604@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 25 Sep 1998 12:38:26 -0500 To: dg@root.com From: "Jeffrey J. Mountin" Subject: Re: PID killed, exceeeded maximum CPU limit... Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <199809251508.IAA24807@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:08 AM 9/25/98 -0700, David Greenman wrote: >> 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? So if a limit in login.conf for the user/class is exceeded it will log? I've never seen it, but know for a fact that Apache has exceeded the maxprocesses and openfiles limits, but no log of this event. Currently I'm seeing a "ps: kvm_getprocs: Cannot allocate memory" and empty ps output from a cron running as root and near as I can tell root doesn't even come close to the limits. This on a PPro w/256MB running 2.2.7 that is a pretty loaded webserver. I've been bit by login classes before. Rather scary that inetd would be killed. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message