svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
ktr(4)
The facility allows kernel events to be logged while the kernel
executes so that they can be examined later when debugging. The
only mandatory option to enable is The option sets the size of
the buffer of events. The size of the buffer in the currently
running kernel can be found via the sysctl By default the buffer
contains 1024 entries. Event levels can be enabled or disabled
to trim excessive and overly verbose logging. First, a mask of
events is specified at compile time via the option to limit which
events are actually compiled into the kernel. The default value
for this option is for all events to be enabled. Secondly, the
actual events logged while the kernel runs can be further masked
via the run time event mask. The option sets the default value
of the run time event mask. The runtime event mask can also be
set by the via the environment variable. It can also be examined
and set after booting via the sysctl. By default the run time
mask is set to block any tracing. The definitions of the event
mask bits can be found in Furthermore, there is a CPU event mask
whose default value can be changed via the option. When two or
more parameters to are used, it is important they are not sepa‐
rated by whitespace. A CPU must have the bit corresponding to
its logical id set in this bitmask for events that occur on it to
be logged. This mask can be set by the via the environment vari‐
able. It can also be examined and set after booting via the
sysctl. By default, only CPUs specified in will log events. See
for more information. By default, events are only logged to the
internal buffer for examination later, but if the verbose flag is
set then they are dumped to the kernel console as well. This
flag can also be set from the loader via the environment vari‐
able, or it can be examined and set after booting via the sysctl.
If the flag is set to zero, which is the default, then verbose
output is disabled. If the flag is set to one, then the contents
of the log message and the CPU number are printed to the kernel
console. If the flag is greater than one, then the filename and
line number of the event are output to the console in addition to
the log message and the CPU number. The option sets the flag to
one. The KTR buffer can be examined from within via the command.
This command displays the contents of the trace buffer one page
at a time. At the prompt, the Enter key displays one more entry
and prompts again. The spacebar displays another page of en‐
tries. Any other key quits. By default the timestamp, filename,
and line number are not displayed with each log entry. If the
modifier is specified, then they are displayed in addition to the
normal output. If the modifier is specified, then just the time‐
stamp is displayed in addition to the normal output. Note that
the events are displayed in reverse chronological order. That
is, the most recent events are displayed first. The option can
be used to log entries to disk for post analysis using the util‐
ity. This option depends on the option. Due to the potentially
high volume of trace messages the trace mask should be selected
carefully. This feature is configured through a group of
sysctls. displays or sets the file that will log to. By default
its value is If the file name is changed while is enabled it will
not take effect until the next invocation. enables logging of
entries to disk if it is set to one. Setting this to 0 will ter‐
minate logging to disk and revert to logging to the normal ktr
ring buffer. Data is not sent to the ring buffer while logging
to disk. is the maximum number of entries that will be recorded
to disk, or 0 for infinite. This is helpful for limiting the
number of particularly high frequency entries that are recorded.
determines the number of entries in the write buffer. This is
the buffer that holds entries before they are written to disk and
defaults to the value of the option. records the number of times
we failed to write an entry due to overflowing the write buffer.
This may happen if the frequency of the logged messages outpaces
the depth of the queue. records the number of entries that have
currently been written to disk. The KTR kernel tracing facility
first appeared in and was imported into