ViewVC Help
View File | Revision Log | Show Annotations | Download File | View Changeset | Root Listing
root/src/trunk/sbin/dumpon/dumpon.8
(Generate patch)

Comparing trunk/sbin/dumpon/dumpon.8 (file contents):
Revision 11226 by laffer1, Sat Dec 7 23:54:44 2013 UTC vs.
Revision 11227 by laffer1, Sun Jul 1 21:09:18 2018 UTC

# Line 1 | Line 1
1 + .\" $MidnightBSD$
2   .\" Copyright (c) 1980, 1991, 1993
3   .\"     The Regents of the University of California.  All rights reserved.
4   .\"
# Line 26 | Line 27
27   .\" SUCH DAMAGE.
28   .\"
29   .\"     From: @(#)swapon.8      8.1 (Berkeley) 6/5/93
30 < .\" $MidnightBSD$
30 > .\" $FreeBSD: stable/10/sbin/dumpon/dumpon.8 306983 2016-10-10 16:17:14Z sevan $
31   .\"
32 < .Dd May 12, 1995
32 > .Dd October 3, 2016
33   .Dt DUMPON 8
34   .Os
35   .Sh NAME
# Line 41 | Line 42
42   .Nm
43   .Op Fl v
44   .Cm off
45 + .Nm
46 + .Op Fl v
47 + .Fl l
48   .Sh DESCRIPTION
49   The
50   .Nm
# Line 56 | Line 60 | controlled by the
60   variable in the boot time configuration file
61   .Pa /etc/rc.conf .
62   .Pp
63 < For most systems the size of the specified dump device must be at
63 > The default type of kernel crash dump is the mini crash dump.
64 > Mini crash dumps hold only memory pages in use by the kernel.
65 > Alternatively, full memory dumps can be enabled by setting the
66 > .Va debug.minidump
67 > .Xr sysctl 8
68 > variable to 0.
69 > .Pp
70 > For systems using full memory dumps, the size of the specified dump
71 > device must be at
72   least the size of physical memory.
73   Even though an additional 64 kB header is added to the dump, the BIOS for a
74   platform typically holds back some memory, so it is not usually
75   necessary to size the dump device larger than the actual amount of RAM
76   available in the machine.
77 < .Pp
66 < The
77 > Also, when using full memory dumps, the
78   .Nm
79   utility will refuse to enable a dump device which is smaller than the
80   total amount of physical memory as reported by the
# Line 72 | Line 83 | total amount of physical memory as reported by the
83   variable.
84   .Pp
85   The
86 + .Fl l
87 + flag causes
88 + .Nm
89 + to print the current dump device or _PATH_DEVNULL ("/dev/null") if no device is
90 + configured.
91 + .Pp
92 + The
93   .Fl v
94   flag causes
95   .Nm
# Line 107 | Line 125 | performs a
125   on
126   .Pa /dev/null
127   and thus instructs the kernel not to save crash dumps.
128 + .Pp
129 + Since
130 + .Nm
131 + cannot be used during kernel initialization, the
132 + .Va dumpdev
133 + variable of
134 + .Xr loader 8
135 + must be used to enable dumps for system panics which occur
136 + during kernel initialization.
137   .Sh FILES
138 < .Bl -tag -width "/dev/{ad,da}?s?b" -compact
139 < .It Pa /dev/{ad,da}?s?b
138 > .Bl -tag -width "/dev/{ada,da}?s?b" -compact
139 > .It Pa /dev/{ada,da}?s?b
140   standard swap areas
141   .It Pa /etc/rc.conf
142   boot-time system configuration
# Line 119 | Line 146 | boot-time system configuration
146   .Xr rc.conf 5 ,
147   .Xr config 8 ,
148   .Xr init 8 ,
149 + .Xr loader 8 ,
150   .Xr rc 8 ,
151   .Xr savecore 8 ,
152   .Xr swapon 8 ,
# Line 127 | Line 155 | boot-time system configuration
155   The
156   .Nm
157   utility appeared in
158 < .Fx 2.1 .
158 > .Fx 2.0.5 .
159   .Sh BUGS
160   Because the file system layer is already dead by the time a crash dump
161   is taken, it is not possible to send crash dumps directly to a file.

Comparing trunk/sbin/dumpon/dumpon.8 (property svn:keywords):
Revision 11226 by laffer1, Sat Dec 7 23:54:44 2013 UTC vs.
Revision 11227 by laffer1, Sun Jul 1 21:09:18 2018 UTC

# Line 0 | Line 1
1 + MidnightBSD=%H

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines