Start syslogd before savecore, so savecore's messages will be logged

properly.  Only users of 4 MB machines might not want it this way (to
prevent accidentally clobbering the coredump), but they are somewhat
in the minority these days.

1 files changed, 10 insertions, 10 deletions

diff --git a/etc/rc b/etc/rc
index cc9cc8b..2c7045c 100644
--- a/etc/rc
+++ b/etc/rc
@@ -1,5 +1,5 @@
 #!/bin/sh
-#	$Id: rc,v 1.141 1997/12/09 10:06:49 danny Exp $
+#	$Id: rc,v 1.142 1997/12/27 19:46:53 steve Exp $
 #	From: @(#)rc	5.27 (Berkeley) 6/5/91
 
 # System startup script run by init on autoboot
@@ -154,15 +154,6 @@ if [ "X${clear_tmp_enable}" = X"YES" ]; then
 	rm -f /tmp/.X*-lock /tmp/.X11-unix/*
 fi
 
-# enable dumpdev so that savecore can see it
-# /var/crash should be a directory or a symbolic link
-# to the crash directory if core dumps are to be saved.
-if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then
-	dumpon ${dumpdev}
-	echo -n checking for core dump...
-	savecore /var/crash
-fi
-
 # snapshot any kernel -c changes back to disk
 echo 'recording kernel -c changes'
 dset -q
@@ -188,6 +179,15 @@ if [ "X${tickadj_enable}" = X"YES" ]; then
 fi
 echo '.'
 
+# enable dumpdev so that savecore can see it
+# /var/crash should be a directory or a symbolic link
+# to the crash directory if core dumps are to be saved.
+if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then
+	dumpon ${dumpdev}
+	echo -n checking for core dump...
+	savecore /var/crash
+fi
+
 if [ -n "$network_pass1_done" ]; then
     network_pass2
 fi