From owner-freebsd-alpha Wed Jul 24 6:29:19 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 78ACB37B400 for ; Wed, 24 Jul 2002 06:29:17 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA3443E4A for ; Wed, 24 Jul 2002 06:29:16 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA14549; Wed, 24 Jul 2002 09:29:16 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6ODSkC01371; Wed, 24 Jul 2002 09:28:46 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15678.43917.910940.94513@grasshopper.cs.duke.edu> Date: Wed, 24 Jul 2002 09:28:45 -0400 (EDT) To: "Schroeder, Aaron" Cc: "'freebsd-alpha@freebsd.org'" Subject: Re: Cron/INetD messages after make world In-Reply-To: <025596A38A894B45AFE62346A6BF47464E2859@waexch1.qgraph.com> References: <025596A38A894B45AFE62346A6BF47464E2859@waexch1.qgraph.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 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