Date: Wed, 24 Dec 2003 18:11:44 -0500 From: "Simon" <simon@optinet.com> To: "Lowell Gilbert" <freebsd-questions-local@be-well.ilk.org> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: New Error Messages :-( Message-ID: <20031224231156.6DB1843D1F@mx1.FreeBSD.org> In-Reply-To: <447k0ln9kt.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ops... I confused maxproc with cputime limit, sorry for the post. The error message being new, made me confuse it with what I thought replaced cputime limit error messages. -Simon On 24 Dec 2003 17:18:42 -0500, Lowell Gilbert wrote: >Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> writes: > >> "Simon" <simon@optinet.com> writes: >> >> > Before version 4.9, FBSD used to print/log: >> > pid 20055 (cmd), uid 1057, was killed: exceeded maximum CPU limit >> > Now, all it prints is: maxproc limit exceeded by uid 1203, please see tuning(7)... >> > making it impossible to identify which process was killed, am I missing something >> > in 4.9 which would make it print the PID killed as well? >> > >> > Any pointers would be appreciated. >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_fork.c?f=u&only_with_tag=RELENG_4&logsort=date >> >> The relevant change was Revision 1.72.2.15, which put a maxproc check >> in a place that hadn't had one at all before. This was a fix to a bug >> (which may have been theoretically present for a long time, but hadn't >> affected any hardware built until recently), so "fixing" this would be >> more complicated than just changing an error string... > >No, I think I'm wrong. The task context is, in fact, available at >that point. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031224231156.6DB1843D1F>