From owner-freebsd-questions Fri Sep 25 10:29:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05555 for freebsd-questions-outgoing; Fri, 25 Sep 1998 10:29:19 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from xwin.webweaver.net (xwin.webweaver.net [208.138.29.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05518; Fri, 25 Sep 1998 10:29:14 -0700 (PDT) (envelope-from nicole@xwin.webweaver.net) Received: by xwin.webweaver.net (VMailer, from userid 1001) id 6A17916812; Fri, 25 Sep 1998 09:29:39 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 In-Reply-To: Date: Fri, 25 Sep 1998 09:29:39 -0700 (PDT) From: Nicole Harrington To: Konrad Heuer Subject: Re: PID killed, exceeeded maximum CPU limit... Cc: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA05532 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> 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 Thanks to everyone who has responded. Inetd is started vi rc.conf as normal. I have altered login.conf lowering the limits for defualt and set up a special group with higher limits etc for Technical employees, however I haven't touched daemon or root and since it sais "uid 0" I would have to assume that it was running with the process time of root which to me is what makes it so odd. This is the second time I have seen this type of error. Last time my qmail process quit with the same error. I start qmail via /usr/local/etc/rc.d/script. Perhaps it is as David Greenman suggested a clock or accounting bug. I am running 2.2.6-RELEASE. Could it just be that I need to increase my max users (currently 128) or some other sysctl setting? But at ~4:00 in the morning, I don't understand what would kill inetd on this machine since the only thing being used via inetd is the qmail pop3. Could this be the result of a hacking attempt? Thanks Nicole nicole@webweaver.net - http://www.webweaver.net/ webmistress@dangermouse.org - http://www.dangermouse.org/ ------------------------------------------------- -- Powered by Coka Cola and FreeBSD -- - Stong enough for a man - But made for a Woman -- -- Microsoft: What bug would you like today? -- - I tried an internal modem once, but it hurt when I walked -- --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message