From owner-freebsd-alpha Wed Jul 24 10:44:29 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42A5C37B401 for ; Wed, 24 Jul 2002 10:44:26 -0700 (PDT) Received: from qescan1.qgraph.com (QESCAN1.qgraph.com [206.158.124.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 964BB43E7B for ; Wed, 24 Jul 2002 10:44:25 -0700 (PDT) (envelope-from Aaron.Schroeder@qg.com) Received: from 192.168.200.28 by qescan1.qgraph.com (InterScan E-Mail VirusWall NT); Wed, 24 Jul 2002 12:43:53 -0500 Received: by sxsmtp1.qgraph.com with Internet Mail Service (5.5.2653.19) id ; Wed, 24 Jul 2002 12:43:52 -0500 Message-ID: <025596A38A894B45AFE62346A6BF47464E287B@waexch1.qgraph.com> From: "Schroeder, Aaron" To: 'Andrew Gallatin' Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: Cron/INetD messages after make world Date: Wed, 24 Jul 2002 12:43:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org That seemed to do the trick! I did a re-compile of the kernel and those messages went away. Thanks Drew! AJ Schroeder -----Original Message----- From: Andrew Gallatin [mailto:gallatin@cs.duke.edu] Sent: Wednesday, July 24, 2002 8:29 AM To: Schroeder, Aaron Cc: 'freebsd-alpha@freebsd.org' Subject: Re: Cron/INetD messages after make world Schroeder, Aaron writes: > Hello all, > > I just recently did a 'portupgrade' and a 'buildworld.' Most everything went > fine, with the exception of kdm not working and these messages on the > console: > > > Jul 23 19:13:01 diabloii inetd[2998]: getting vmemoryuse resource limit: > Invalid argument > > Jul 23 19:15:00 diabloii /usr/sbin/cron[3000]: getting vmemoryuse resource > limit: Invalid argument > > I have not played with inetd in a long time on this machine and I have never > touched cron. Got me hanging as to what they may be. > > Anyone have any ideas? I don't hink this is alpha specifc. It doesn't sound like you rebuilt your kernel & rebooted. See freebsd-stable archives. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message