From owner-freebsd-current Wed Sep 13 12:04:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA21910 for current-outgoing; Wed, 13 Sep 1995 12:04:36 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA21897 for ; Wed, 13 Sep 1995 12:04:31 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id UAA07116 for FreeBSD-current@FreeBSD.org; Wed, 13 Sep 1995 20:04:28 +0100 From: Paul Richards Message-Id: <199509131904.UAA07116@server.netcraft.co.uk> Subject: syslogd problems To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Wed, 13 Sep 1995 20:04:28 +0100 (BST) Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 814 Sender: current-owner@FreeBSD.org Precedence: bulk Having "fixed" syslogd to not do an unconditional unlink at startup I've now got a related problem. If the machine crashes then the /dev/log file still exists and syslogd doesn't start up after boot. I still think that the fix is correct since the previous behaviour was too dangerous, there needs to be some method to cleanup after a crash though. Ideas: 1) Make syslogd more intelligent so it stats the file and sees if it's a socket. What happens if the pathname is something else's socket? 2) Removes the PATH_LOG file, probably check it's a socket just to be safe. 3) Remove /dev/log in /etc/rc before starting syslogd. (nice and easy :-) Any thoughts. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work)