From owner-freebsd-questions@FreeBSD.ORG  Wed Dec 24 15:42:56 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 AF3EF16A4CE
	for <freebsd-questions@freebsd.org>;
	Wed, 24 Dec 2003 15:42:56 -0800 (PST)
Received: from be-well.no-ip.com (lowellg.ne.client2.attbi.com [66.30.200.37])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E03A943D2F
	for <freebsd-questions@freebsd.org>;
	Wed, 24 Dec 2003 15:42:55 -0800 (PST)
	(envelope-from freebsd-questions-local@be-well.ilk.org)
Received: by be-well.no-ip.com (Postfix, from userid 1147)
	id 2DAF266; Wed, 24 Dec 2003 18:42:55 -0500 (EST)
Sender: lowell@be-well.ilk.org
To: "Simon" <simon@optinet.com>
References: <20031224231156.6DB1843D1F@mx1.FreeBSD.org>
From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
Date: 24 Dec 2003 18:42:54 -0500
In-Reply-To: <20031224231156.6DB1843D1F@mx1.FreeBSD.org>
Message-ID: <441xqtn5oh.fsf@be-well.ilk.org>
Lines: 7
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
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:42:56 -0000

"Simon" <simon@optinet.com> 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.