strerr(1m) [opensolaris man page]
strerr(1M) System Administration Commands strerr(1M) NAME
strerr - STREAMS error logger daemon SYNOPSIS
strerr DESCRIPTION
strerr receives error log messages from the STREAMS-based log driver (see log(7D)) and appends them to a log file. The resultant error log files reside in the directory /var/adm/streams, and are named error.mm-dd, where mm is the month and dd is the day of the messages con- tained in each log file. The format of an error log message is: <seq> <time> <ticks> <flags> <mid> <sid> <text> <seq> error sequence number <time> time of message in hh:mm:ss <ticks> time of message in machine ticks since boot priority level <flags> T : the message was also sent to a tracing process F : indicates a fatal error N : send mail to the system administrator (hard- coded as root) <mid> module ID number of source <sid> sub-ID number of source <text> formatted text of the error message Messages that appear in the error log are intended to report exceptional conditions that require the attention of the system administrator. Those messages which indicate the total failure of a STREAMS-based driver or module should have the F flag set. Those messages requiring the immediate attention of the administrator will have the N flag set, which causes the error logger to send the message to the system administrator using mail. The priority level usually has no meaning in the error log but will have meaning if the message is also sent to a tracer process. Once initiated, strerr continues to execute until terminated by the user. It is commonly executed asynchronously. FILES
/var/adm/streams/error.mm-dd error log file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5), log(7D) NOTES
There is no restriction to the number of strerr processes opening the STREAMS-based log driver at a time. If a module or driver is generating a large number of error messages, running the error logger will cause a degradation in STREAMS perfor- mance. If a large burst of messages are generated in a short time, the log driver may not be able to deliver some of the messages. This situation is indicated by gaps in the sequence numbering of the messages in the log files. SunOS 5.11 4 Oct 1994 strerr(1M)
Check Out this Related Man Page
strace(8) System Manager's Manual strace(8) NAME
strace - Writes STREAMS event trace messages to standard output SYNOPSIS
/usr/sbin/strace [mod_ID sub_ID pri_level] DESCRIPTION
The strace command gets STREAMS event trace messages from STREAMS drivers and modules via the STREAMS log driver (strlog), and writes these messages to standard output. You can limit the messages strace receives by specifying arguments to the command. The arguments, which must be specified together, are the following: Specifies the STREAMS module identification number. Specifies a subidentification number (often corresponding to a minor device). Specifies a tracing priority level. The strace command will get messages of a level equal to or less than the value in the pri_level argument. The value of the argument must be a nonnegative integer. You can specify all as the value for any of the arguments in the strace command line. The value all indicates that there are no restric- tions for that argument. You can also specify multiple sets of the command's three arguments to obtain the messages from more than one driver or module. More than one strace process can open the STREAMS log driver at a time. When you invoke strace, the log driver compares the sets of argu- ments from the command line with actual trace messages, returning the messages that satisfy the criteria. STREAMS event trace messages have the following format: seqnum stdtime tickstime pri_level ntfycode mod_ID sub_ID msgtext where: The event trace sequence number. The time the message was sent, in the format hh:mm:ss. The time the message was sent, measured in machine ticks since the last boot. The tracing priority level as defined by the STREAMS driver or module that originates the messages. Can be either of the following indicators: Indicates that the message has also been saved in the error log. Indicates that the message signaled a fatal error. The module identification number of the trace message source. The subidentification number of the trace message source. The trace message text. The strace command runs until terminated by the user. NOTES
Running strace with several sets of arguments can negatively affect STREAMS performance, particularly for those modules and drivers sending the messages. Also be aware that strace may not be able to handle a large number of messages. If drivers and modules return messages to strace too quickly, some may be lost. EXAMPLES
To display all trace messages received from the driver or module identified by mod_ID 28, enter: strace 28 all all To display those trace messages from the driver or module identified by mod_ID 28 and its minor devices identified by the sub_IDs 2, 3, and 4, enter: strace 28 2 all 28 3 all 28 4 all This command line causes messages of any tracing priority level to be displayed. To display the trace messages from the same driver or module and sub_IDs, but limited to certain priority levels, enter: strace 28 2 0 28 3 0 28 4 1 This command line specifies that messages from driver or module 28 and sub_IDs 2 and 3 must have a tracing priority of 0, and those from sub_ID 4 must have a tracing priority equal to or less than 1. RELATED INFORMATION
Commands: strclean(8), strerr(8). Interfaces: strlog(7). delim off strace(8)