"Simon" <[EMAIL PROTECTED]> 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.


The relevant change was Revision, 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"
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to