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.
On 24 Dec 2003 17:18:42 -0500, Lowell Gilbert wrote:
>Lowell Gilbert <[EMAIL PROTECTED]> writes:
>> "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 22.214.171.124, 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
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"