New Error Messages :-(
Lowell Gilbert
freebsd-questions-local at be-well.ilk.org
Wed Dec 24 14:18:45 PST 2003
Lowell Gilbert <freebsd-questions-local at be-well.ilk.org> writes:
> "Simon" <simon at 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.
More information about the freebsd-questions
mailing list