From owner-freebsd-questions@FreeBSD.ORG Tue Jan 6 07:12:41 2004 Return-Path: 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 1A6B616A4CE for ; Tue, 6 Jan 2004 07:12:41 -0800 (PST) Received: from sferics.mongueurs.net (sferics.mongueurs.net [81.80.147.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55C5743D31 for ; Tue, 6 Jan 2004 07:12:39 -0800 (PST) (envelope-from david@landgren.net) Received: from landgren.net (81-80-147-206.bpinet.com [81.80.147.206]) by sferics.mongueurs.net (Postfix) with ESMTP id ED2C1E6BB for ; Tue, 6 Jan 2004 16:12:37 +0100 (CET) Message-ID: <3FFACFE7.8080505@landgren.net> Date: Tue, 06 Jan 2004 16:10:31 +0100 From: David Landgren Organization: The Dusty Decadent Delights of Imperial Pompeii User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ps: warning: /var/run/dev.db: No such file or directory X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2004 15:12:41 -0000 I recently rebooted a server that had been running for many months. I haven't touched the kernel or userland programs since it went into production. The server was rebooted with 'shutdown -h now', powered down, and then later restarted. I've since noticed that cron didn't restart, which is odd, but fixable, but more importantly, when I run ps, it spits out 'ps: warning: /var/run/dev.db: No such file or directory' (although, as far as I can tell, the output is perfectly reasonable). I'm wondering if one is a symptom of the other. In any event, /var/run/dev.db is most certainly not there. I guess I could reboot the server tonight, but I'm not sure that that will fix it, as I don't understand the cause. I've searched the archives a bit, and the best thread I could find dated from 1997, and suggested that it could be due to an unclean shutdown, which is definitely not the case here. I'm running FreeBSD 4.8-STABLE, where stable is defined as being what it was around June 2003. I'd be grateful for any pointers you might have. Thanks, David -- Commercial OS breeds commerce, whereas free OS breeds freedom, the only thing more dangerous and confusing than commerce. -- Michael R. Jinks, redhat-list, circa 1997