This topic describes the log, trace, and system dump mechanisms for the Solaris client.
The Solaris client provides log, trace, and system dump mechanisms.
Use the syslog utility to enable logging on a Solaris client. The log messages are routed through the syslog utility on the Solaris operating system. The syslog utility captures log output from the kernel, as well as other operating system services. By default, the syslog utility discards all kernel output. However, you can configure the syslog utility to specify a destination for the messages by modifying the/etc/syslog.conf file.
The trace messages are recorded in a memory-based trace buffer. The trace buffer is a circular buffer. Trace messages are overwritten with new messages when the buffer overflows.
First failure tracing is enabled by default and cannot be disabled. All other tracing levels are disabled by default and can be enabled using the sanfstrace set utility. You can also use the sanfstrace utility to set and list levels of tracing.
You can use sanfstrace log utility to retrieve the logged trace messages from the trace buffer and append them in text format to a specified log file. If you do not specify a file, the messages are sent to the standard output device.
The Solaris operating system automatically creates a disk copy of the physical memory when a system crash occurs. This disk copy is known as a crash dump. The crash dump information is saved in a set of files named unix.x and vmcore.x, where x is an integer that identifies the dump. You can configure the directory in which these files are stored and can set other dump parameters using the dumpadm utility.
Parent topic: Client logs and traces