Date: Fri, 25 Sep 1998 12:38:26 -0500 From: "Jeffrey J. Mountin" <jeff-ml@mountin.net> To: dg@root.com Cc: freebsd-isp@FreeBSD.ORG Subject: Re: PID killed, exceeeded maximum CPU limit... Message-ID: <3.0.3.32.19980925123826.006e1604@207.227.119.2> In-Reply-To: <199809251508.IAA24807@implode.root.com> References: <Your message of "Fri, 25 Sep 1998 05:01:24 PDT." <XFMail.980925050124.freelist@webweaver.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19980925123826.006e1604>