|
Lines 68-75
Link Here
|
| 68 |
.Nm |
68 |
.Nm |
| 69 |
to be verbose about its activity. |
69 |
to be verbose about its activity. |
| 70 |
.Sh NOTES |
70 |
.Sh NOTES |
| 71 |
One of the system swap devices is usually chosen as the dump device, as |
71 |
One of the system swap devices should be used as the dump device. Devices |
| 72 |
swap devices are the most likely to have the required space at dump time. |
72 |
used for regular filesystems will probably lack sufficent space to store the |
|
|
73 |
dump. |
| 73 |
.Pp |
74 |
.Pp |
| 74 |
The |
75 |
The |
| 75 |
.Nm |
76 |
.Nm |
|
Lines 106-114
Link Here
|
| 106 |
Because the filesystem layer is already dead by the time a crash dump |
107 |
Because the filesystem layer is already dead by the time a crash dump |
| 107 |
is taken, it is not possible to send crash dumps directly to a file. |
108 |
is taken, it is not possible to send crash dumps directly to a file. |
| 108 |
.Pp |
109 |
.Pp |
| 109 |
.Nm Dumpon |
110 |
Since |
| 110 |
currently allows only devices with minor number 1 to be used as dump |
111 |
.Nm dumpon |
| 111 |
devices. |
112 |
is called from |
|
|
113 |
.Pa /etc/rc , |
| 114 |
system panics during kernel initialisation or single-user mode will NOT |
| 115 |
cause a dump. Currently, there is no safe or reliable way to enforce |
| 116 |
the creation of dumps in these cases. |
| 112 |
.Sh HISTORY |
117 |
.Sh HISTORY |
| 113 |
The |
118 |
The |
| 114 |
.Nm |
119 |
.Nm |