Date: Fri, 25 Sep 1998 17:58:55 +0200 (CEST) From: Konrad Heuer <kheuer@gwdu60.gwdg.de> To: Nicole <freelist@webweaver.net> Cc: freebsd-isp@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: PID killed, exceeeded maximum CPU limit... Message-ID: <Pine.BSF.3.96.980925174851.3311A-100000@gwdu60.gwdg.de> In-Reply-To: <XFMail.980925050124.freelist@webweaver.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Sep 1998, Nicole 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 Sounds strange. Normally there should no CPU time limit for the daemon processes. Please check login class "daemon" in "/etc/login.conf". The corresponding entry should be ":cputime=infinity:". If nothings works insert the line ulimit -t unlimited at the beginning of your "/etc/rc" file. But before doing that ypu should ask yourself how "inetd" has been started before. May be someone knowing the root password started "inetd" manually after problems from a shell with a CPU time limit set? Ok, the pid is small, so that's unlikely, but ... Konrad Heuer // Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH // Goettingen (GWDG), Am Fassberg, D-37077 Goettingen, Germany // // kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980925174851.3311A-100000>