svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
textdump(4)
The facility allows the capture of kernel debugging information
to disk in a human-readable rather than the machine-readable form
normally used with kernel memory dumps and minidumps. This rep‐
resentation, while less complete in that it does not capture full
kernel state, can provide debugging information in a more com‐
pact, portable, and persistent form than a traditional dump. By
combining with other facilities, such as scripting and output
capture, detailed bug information can be captured in a fully au‐
tomated manner. data is stored in a dump partition in the same
style as a regular memory dump, and will be automatically ex‐
tracted by if present on boot. files are stored in the format,
and consist of one or more text files, each storing a particular
type of debugging output. The following parts may be present:
Captured output, if the capture facility has been used. May be
disabled by clearing the sysctl. Kernel configuration, if has
been compiled into the kernel. May be disabled by clearing the
sysctl. Kernel message buffer, including recent console output
if the capture facility has been used. May be disabled by clear‐
ing the sysctl. Kernel panic string, if the kernel panicked be‐
fore the dump was generated. May be disabled by clearing the
sysctl. Kernel version string. My be disabled by clearing the
sysctl. Kernel textdumps may be extracted using The facility is
enabled as part of the kernel debugger using and By default, ker‐
nel dumps generated on panic or via explicit requests for a dump
will be regular memory dumps; however, by using the command in or
by setting the sysctl to 1 using it is possible to request that
the next dump be a textdump. One may also directly trigger a
textdump in by running the command If at the command line, the
commands and may be used to set, query, and clear the textdump
pending flag. As with regular kernel dumps, a dump partition
must be automatically or manually configured using Additional
kernel options: sets textdumps to be the default manner of doing
dumps. This means there will be no need to or use the commands.
will have the textdump facility be more verbose about each file
it is emitting as well as other diagnostics useful to debug the
textdump facility itself. In the following example, the script
will run when the kernel debugger is entered as a result of a
panic, enable output capture, dump several useful pieces of de‐
bugging information, and then invoke panic in order to force a
kernel dump to be written out followed by a reboot: script
kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllocks; call doadump; reset In the follow‐
ing example, the script will run when the kernel debugger is en‐
tered as a result of a witness violation, printing lock-related
information for the user: script kdb.enter.witness=show locks
These scripts may also be configured using the utility. The fa‐
cility first appeared in The facility was created by