1 .\" Copyright (c) 1980, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" From: @(#)savecore.8 8.1 (Berkeley) 6/5/93
36 .Nd "save a core dump of the operating system"
50 .Op Ar directory Op Ar device ...
55 copies a core dump into
57 or the current working directory if no
60 and enters a reboot message and information about the core dump into
63 The options are as follows:
64 .Bl -tag -width ".Fl m Ar maxdumps"
68 in a selection of different human and machine readable formats.
71 for details on command line arguments.
73 Check to see if a dump exists,
74 and display a brief message to indicate the status.
75 An exit status of 0 indicates that a dump is there,
76 1 indicates that none exists.
77 This option is compatible only with the
81 Clear the dump, so that future invocations of
85 Force a dump to be taken even if either the dump was cleared or if the
86 dump header information is inconsistent.
88 Do not clear the dump after saving it.
90 Maximum number of dumps to store.
91 Once the number of stored dumps is equal to
93 the counter will restart from
96 Print out some additional debugging information.
97 Specify twice for more information.
99 Compress the dump (see
101 The dump may already be compressed if the kernel was configured to
104 In this case, the option has no effect.
110 looks for dumps on each device specified by the
112 argument(s), or on each device in
121 checks the core dump in various ways to make sure that it is complete.
122 If it passes these checks, it saves the core image in
123 .Ar directory Ns Pa /vmcore.#
124 and information about the core in
125 .Ar directory Ns Pa /info.# .
126 If the core is encrypted, it saves the dump key in
127 .Ar directory Ns Pa /key.# .
128 The core can be later decrypted using
130 For kernel textdumps generated with the
132 facility, output will be stored in the
135 .Ar directory Ns Pa /textdump.tar.# .
138 is the number from the first line of the file
139 .Ar directory Ns Pa /bounds ,
140 and it is incremented and stored back into the file each time
147 also checks the available disk space before attempting to make the copies.
148 If there is insufficient disk space in the file system containing
151 .Ar directory Ns Pa /minfree
152 exists and the number of free kilobytes (for non-superusers) in the
153 file system after the copies were made would be less than the number
154 in the first line of this file, the copies are not attempted.
158 successfully copies the kernel and the core dump, the core dump is cleared
159 so that future invocations of
166 is meant to be called near the end of the initialization file
174 .Xr xo_parse_args 3 ,
186 Support for kernel textdumps appeared in
189 The minfree code does not consider the effect of compression or sparse files.