From root@champagne.caida.org  Mon Jan 26 18:42:09 1998
Received: from champagne.caida.org (ncsa-ipv6.ncsa.uiuc.edu [141.142.121.4])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18798
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 26 Jan 1998 18:42:07 -0800 (PST)
          (envelope-from root@champagne.caida.org)
Received: (from root@localhost)
	by champagne.caida.org (8.8.5/8.8.5) id SAA00637;
	Mon, 26 Jan 1998 18:39:50 -0600 (CST)
Message-Id: <199801270039.SAA00637@champagne.caida.org>
Date: Mon, 26 Jan 1998 18:39:50 -0600 (CST)
From: jhawk@nlanr.net
Reply-To: jhawk@nlanr.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: syslogds starts before savecore
X-Send-Pr-Version: 3.2

>Number:         5576
>Category:       bin
>Synopsis:       syslogd should start before savecore
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jan 26 18:50:01 PST 1998
>Closed-Date:    Mon May 4 09:28:48 PDT 1998
>Last-Modified:  Mon May  4 09:31:06 PDT 1998
>Originator:     John Hawkinson
>Release:        FreeBSD 2.2.1-RELEASE i386
>Organization:
NLANR
>Environment:

	

>Description:

	savecore runs before syslogd in /etc/rc. This means
	that if savecore fails (for instance, the disk is full)
	then it's diagnostics are not preserved.

>How-To-Repeat:

	Cause a machine with a full /var/crash to to panic; observe
	there is no way to determine why the machine rebooted from
	looking at logs, etc., etc. No crash dumps in /var/crash,
	of course, etc., etc.

>Fix:
	
	Re-order /etc/rc such that savecore runs after syslogd.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: dt 
State-Changed-When: Mon May 4 09:28:48 PDT 1998 
State-Changed-Why:  
This is fixed now. 
>Unformatted:
