From owner-freebsd-stable  Sun Aug 18 17:15:19 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 16E9237B400
	for <stable@FreeBSD.ORG>; Sun, 18 Aug 2002 17:15:16 -0700 (PDT)
Received: from obsidian.sentex.ca (obsidian.sentex.ca [64.7.128.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7161943E3B
	for <stable@FreeBSD.ORG>; Sun, 18 Aug 2002 17:15:15 -0700 (PDT)
	(envelope-from mike@sentex.net)
Received: from simian.sentex.net (pyroxene.sentex.ca [199.212.134.18])
	by obsidian.sentex.ca (8.12.5/8.12.5) with ESMTP id g7J0F9Co088221;
	Sun, 18 Aug 2002 20:15:09 -0400 (EDT)
	(envelope-from mike@sentex.net)
Message-Id: <5.1.1.6.0.20020818201453.030e4da0@marble.sentex.ca>
X-Sender: mdtpop@marble.sentex.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Sun, 18 Aug 2002 20:15:38 -0400
To: "Hutterer" <robert.hutterer@univie.ac.at>, <stable@FreeBSD.ORG>
From: Mike Tancsa <mike@sentex.net>
Subject: Re: WG: WRONG CRONJOB?
In-Reply-To: <003001c24714$ed8b1bb0$0800a8c0@p4>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: By Sentex Communications (obsidian/20020220)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG


Did you update /etc/login.conf and then cap_mkdb /etc/login.conf ?

         ---Mike

At 02:11 AM 19/08/2002 +0200, Hutterer wrote:
>I am running ver. 4.6.2-RELEASE.
>
>After upgrading over a cvs-renewed tree of src (release=cvs tag=RELENG_4)
>
>and using make world
>
>I get on  and on this system message
>
>Aug 19 01:15:00 elearn /usr/sbin/cron[727]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:15:00 elearn /usr/sbin/cron[727]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:20:00 elearn /usr/sbin/cron[730]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:20:00 elearn /usr/sbin/cron[730]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:25:00 elearn /usr/sbin/cron[733]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:25:00 elearn /usr/sbin/cron[733]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:30:00 elearn /usr/sbin/cron[736]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:30:00 elearn /usr/sbin/cron[736]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:31:00 elearn /usr/sbin/cron[739]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:31:00 elearn /usr/sbin/cron[739]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:35:00 elearn /usr/sbin/cron[742]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:35:00 elearn /usr/sbin/cron[742]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:40:00 elearn /usr/sbin/cron[746]: getting vmemoryuse resource 
>limit: Invalid argument
>
>Aug 19 01:40:00 elearn /usr/sbin/cron[746]: getting vmemoryuse resource 
>limit: Invalid argument
>
>&
>
>&..
>
>
>
>Does anybody know how to stop this??
>
>
>
>Thanks


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message