From owner-freebsd-current Wed Dec 10 11:35:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA10830 for current-outgoing; Wed, 10 Dec 1997 11:35:22 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA10822 for ; Wed, 10 Dec 1997 11:35:17 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id NAA29304; Wed, 10 Dec 1997 13:34:27 -0600 (CST) From: Kevin Day Message-Id: <199712101934.NAA29304@home.dragondata.com> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <19971210114226.23033@mcs.net> from Karl Denninger at "Dec 10, 97 11:42:26 am" To: karl@mcs.net (Karl Denninger) Date: Wed, 10 Dec 1997 13:34:27 -0600 (CST) Cc: toor@dyson.iquest.net, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok... A bit of progress... I figured out which user has the problem... The usr chronos is running an eggdrop... I tried to 'su' to his user name, so I could run things somewhat safely... After I su to him, all I get is 'su: fork: Resource temporarily unavailable'. What's going on, and does this have anything to do with his cron job crashing the system? $ su Password: You have mail. shell# su toasty $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 1835919 571239 1117807 34% / procfs 4 4 0 100% /proc $ ^D shell# su chronos bash$ df su: fork: Resource temporarily unavailable bash$ ulimit unlimited bash$ ls su: fork: Resource temporarily unavailable bash$ Kevin