Better section name

[ikiwiki.git] / docs / howtos / HowToCreateACoreDump.mdwn

diff --git a/docs/howtos/HowToCreateACoreDump.mdwn b/docs/howtos/HowToCreateACoreDump.mdwn
index 8950a31..3a685b6 100644 (file)
--- a/docs/howtos/HowToCreateACoreDump.mdwn
+++ b/docs/howtos/HowToCreateACoreDump.mdwn
@@ -1,5 +1,6 @@
 # Getting a system core dump 
-[[!toc levels=3 ]]�  A full system core dump (also called post-mortem dump) is sometimes needed to track down a bug in the DragonFlyBSD kernel.
+[[!toc levels=3 ]]
+A full system core dump (also called post-mortem dump) is sometimes needed to track down a bug in the DragonFlyBSD kernel.
 
 Please note: A full core dump is obtained by triggering a kernel panic. Like when pulling the power plug from the wall socket, unsaved data will be lost, recently saved data might be lost, and filesystems mounted async might be destroyed.
 
@@ -55,6 +56,9 @@ If the machine has dropped to a dbb> prompt by itself you can type the following
 
 During the following startup the core dump will be automatically saved to `/var/crash`.
 
+# Getting a coredump on a remote machine
+Set debug.debugger_on_panic to 0 or configure your kernel with options DDB_UNATTENDED.
+
 # Useful hints 
 
 * You can have the settings described above take effect without rebooting using the following commands: