From owner-cvs-usrsbin Fri Jan 3 08:20:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA00110 for cvs-usrsbin-outgoing; Fri, 3 Jan 1997 08:20:58 -0800 (PST) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA00102; Fri, 3 Jan 1997 08:20:46 -0800 (PST) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.4/8.8.4) with ESMTP id AAA25916; Sat, 4 Jan 1997 00:19:21 +0800 (WST) Message-Id: <199701031619.AAA25916@spinner.DIALix.COM> X-Mailer: exmh version 2.0beta 12/23/96 To: "Jordan K. Hubbard" cc: Paul Richards , CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-usrsbin@freefall.freebsd.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c In-reply-to: Your message of "Fri, 03 Jan 1997 08:03:34 PST." <23562.852307414@time.cdrom.com> Date: Sat, 04 Jan 1997 00:19:21 +0800 From: Peter Wemm Sender: owner-cvs-usrsbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" wrote: > > These signals should all unlink LogName when syslogd dies. > > And it's undoubtedly some other signal, like SIGSEGV :) Hmm. Our console logger seems to not print messages on the console while /dev/klog is open, is that right? (This probably would prevent the "syslogd died signal 11 message on the console since it would be sent to syslogd's open file handle that had not yet closed on exit). I wonder if we should put in a defensive catcher for the common fatal signals (SEGV,BUS) that does a bare bones log and exit? > Jordan Cheers, -Peter