From owner-freebsd-questions@FreeBSD.ORG  Wed Dec 24 15:11:59 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EEC9C16A4CE
	for <freebsd-questions@freebsd.org>;
	Wed, 24 Dec 2003 15:11:58 -0800 (PST)
Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net
	[207.99.79.37])	by mx1.FreeBSD.org (Postfix) with SMTP id 6DB1843D1F
	for <freebsd-questions@freebsd.org>;
	Wed, 24 Dec 2003 15:11:56 -0800 (PST)
	(envelope-from simon@optinet.com)
Received: (qmail 71717 invoked by uid 110); 24 Dec 2003 23:13:32 -0000
Received: from ool-18baaf5c.dyn.optonline.net (HELO win2kpc1) (24.186.175.92)
  by cobra.acceleratedweb.net with SMTP; 24 Dec 2003 23:13:32 -0000
From: "Simon" <simon@optinet.com>
To: "Lowell Gilbert" <freebsd-questions-local@be-well.ilk.org>
Date: Wed, 24 Dec 2003 18:11:44 -0500
Priority: Normal
X-Mailer: PMMail 2000 Professional (2.20.2661) For Windows 2000 (5.0.2195;4)
In-Reply-To: <447k0ln9kt.fsf@be-well.ilk.org>
MIME-Version: 1.0
Message-Id: <20031224231156.6DB1843D1F@mx1.FreeBSD.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.1
cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject: Re: New Error Messages :-(
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Dec 2003 23:11:59 -0000


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 <freebsd-questions-local@be-well.ilk.org> writes:
>
>> "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...
>
>No, I think I'm wrong.  The task context is, in fact, available at
>that point.
>