DragonFly BSD
DragonFly bugs List (threaded) for 2010-04
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[issue1734] savecore is not picking up dumpdev if the device is not also swap

From: "Alexander Polakov \(via DragonFly issue tracker\)" <sinknull@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 15 Apr 2010 17:15:48 +0000

Alexander Polakov <polachok@gmail.com> added the comment:

I was wrong. savecore doesn't look on dumpdev at all.

We can do something like this, I guess:

diff --git a/etc/rc.d/savecore b/etc/rc.d/savecore
index bc62b77..f55aff1 100644
--- a/etc/rc.d/savecore
+++ b/etc/rc.d/savecore
@@ -58,7 +58,7 @@ savecore_start()
        if [ X$dumpdev != X ]; then
                echo "Checking for core dump..."
-               savecore ${savecore_flags} ${DUMPDIR}
+               savecore ${savecore_flags} ${DUMPDIR} ${dumpdev}
                return ${RC_CONFIGURED}

diff --git a/share/man/man5/rc.conf.5 b/share/man/man5/rc.conf.5
index c7128fb..4329fe5 100644
--- a/share/man/man5/rc.conf.5
+++ b/share/man/man5/rc.conf.5
@@ -2315,7 +2315,9 @@ to turn this behavior off.
 Indicates the device (usually a swap partition) to which a crash dump
 should be written in the event of a system crash.
 The value of this variable is passed as the argument to
-.Xr dumpon 8 .
+.Xr dumpon 8
+.Xr savecore 8 .
 To disable crash dumps, set this variable to
 .Dq Li NO .
 .It Va dumpdir

DragonFly issue tracker <bugs@lists.dragonflybsd.org>

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]