Date: Sun, 2 Jul 1995 13:50:03 -0700 From: peter@haywire.dialix.com (Peter Wemm) To: freebsd-bugs Subject: conf/584: bad setting for dumpdev in sample sysconfig Message-ID: <199507022050.NAA09799@freefall.cdrom.com> In-Reply-To: Your message of Mon, 3 Jul 1995 04:40:35 %2B0800 <199507022040.EAA00387@jhome.DIALix.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
>Number: 584
>Category: conf
>Synopsis: bad setting for dumpdev in sample sysconfig
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs (FreeBSD bugs mailing list)
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jul 2 13:50:02 1995
>Originator: Peter Wemm
>Organization:
DIALix Services
>Release: FreeBSD 2.0-BUILT-19950703 i386
>Environment:
FreeBSD-current, as of a few hours ago..
FreeBSD jhome.DIALix.COM 2.0-BUILT-19950703 FreeBSD 2.0-BUILT-19950703 #11: Mon Jul 3 04:17:24 WST 1995 pwroot@jhome.DIALix.COM:/usr/src/sys/compile/JHOME i386
>Description:
/etc/rc checks the setting of $dumpdev, and skips it if it's set to
NO. The matching sysconfig file however, doesn't set it.
/etc/rc then runs dumpon ${dumpdev} (because it's not "NO")
and causes usage errors during startup.
>How-To-Repeat:
install distributed sysconfig file (and customize it for your host
of course.. :-)
>Fix:
Something like this might be appropriate..
--- sysconfig.nodumpdev Sun Jun 25 16:32:11 1995
+++ sysconfig Mon Jul 3 04:31:52 1995
@@ -147,7 +147,7 @@
# disable any statically configured dumpdev, or NO to do nothing.
# The device should normally be one of the swap devices specified
# in /etc/fstab.
-# dumpdev=/dev/sd0b
+dumpdev=NO
# Set to YES if you want kernel crashdumps to be saved for debugging
savecore=NO
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507022050.NAA09799>