diff options
Diffstat (limited to '')
-rw-r--r-- | doc/new_chapters/eventlog.t | 27 |
1 files changed, 22 insertions, 5 deletions
diff --git a/doc/new_chapters/eventlog.t b/doc/new_chapters/eventlog.t index 556a6ea8b8..0dfefa146e 100644 --- a/doc/new_chapters/eventlog.t +++ b/doc/new_chapters/eventlog.t @@ -41,11 +41,28 @@ The directives provided by the event logging manager are: @subsection Log Files and Events -System log - -Non-system logs - -Events, facility, severity +The operating system uses a special log file named @code{XXX}. +This log file is called the system log and is automatically created and +tracked by the operating system. The system log is written to with +the @code{log_write} function. An alternative log file may be written +using the @code{log_write_any} function. It is possible to use @code{log_read} +to query the system and @code{log_write_entry} to a non-system log file +to produce a filtered version of the system log. For example you could +produce a log of all disk controller faults that have occurred. + +A non-system log may be a special log file created by an application to +describe application faults, or a subset of the system log created +by the application. + +A facility is an identification code for a subsystem, device, or +other object about which information is being written to +a log file. Severity is a rating of the error that is being logged. +The facility identifier and the event severity are the basis for +subsequent log query. A log query is used as a filter to +obtain a subset of a given log file. The log file may be configured +to send out an event ... ??? + +XXX Events @subsection Queries |