"Simon" <[EMAIL PROTECTED]> writes:
> 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.
I have a patch, anyway.
___
[EMAIL PRO
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 <[EMAIL PROTECTED]> writes:
>
>> "Simon" <[EMA
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)...
> > makin
"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
Hi,
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
