Skip site navigation (1)Skip section navigation (2)
Date:      24 Dec 2003 17:15:08 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        "Simon" <simon@optinet.com>
Cc:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: New Error Messages :-(
Message-ID:  <44brpxn9qr.fsf@be-well.ilk.org>
In-Reply-To: <20031223171606.7E8EF43D49@mx1.FreeBSD.org>
References:  <20031223171606.7E8EF43D49@mx1.FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
"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...

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area: 
		resume/CV at http://be-well.ilk.org:8088/~lowell/resume/
		username/password "public"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44brpxn9qr.fsf>