| SAVECORE(8) | System Manager's Manual | SAVECORE(8) | 
savecore —
| savecore | [ -fvz] [-Nsystem] [-Zlevel] [directory] | 
| savecore | -c[-v]
      [-Nsystem] | 
| savecore | -n[-v]
      [-Nsystem] | 
Upon a subsequent reboot, savecore is
    typically run out of rc(8), before
    swapping is enabled, to copy the kernel and the saved memory image into
    directory, and enters a reboot message and information
    about the core dump into the system log. If a directory is not specified,
    then /var/crash is used.
The kernel and core file can then be analyzed using various tools, including crash(8), dmesg(8), fstat(1), gdb(1), iostat(8), netstat(1), ps(1), and pstat(8), to attempt to deduce the cause of the crash.
Crashes are usually the result of hardware faults or kernel bugs. If a kernel bug is suspected, a full bug report should be filed at http://www.netbsd.org/, or using send-pr(1), containing as much information as possible about the circumstances of the crash. Since crash dumps are typically very large and may contain whatever (potentially confidential) information was in memory at the time of the crash, do NOT include a copy of the crash dump file in the bug report; instead, save it somewhere in the event that a NetBSD developer wants to examine it.
The options are as follows:
-csavecore will ignore it.-f-n-N-v-z-Z
    level-z to
      level. Defaults to 1 (the fastest compression mode).
      Refer to gzip(1) for more
      information regarding the compression level.savecore checks the core dump in various
    ways to make sure that it is current and that it corresponds to the
    currently running system. If it passes these checks, it saves the core image
    in directory/netbsd.#.core and
    the system in
    directory/netbsd.# (or in
    directory/netbsd.#.core.gz and
    directory/netbsd.#.gz,
    respectively, if the -z option is used). The
    “#” is the number from the first line of the file
    directory/bounds, and it is
    incremented and stored back into the file each time
    savecore successfully runs.
savecore also checks the available disk
    space before attempting to make the copies. If there is insufficient disk
    space in the file system containing directory, or if
    the file directory/minfree
    exists and the number of free kilobytes (for non-superusers) in the file
    system after the copies were made would be less than the number in the first
    line of this file, the copies are not attempted.
If savecore successfully copies the kernel
    and the core dump, the core dump is cleared so that future invocations of
    savecore will ignore it.
savecore command appeared in
  4.1BSD.
| September 13, 2011 | NetBSD 10.1 |