Home   Info   DevZone   Wiki   UsersWeb  |  MainWeb  |  InfoWeb  |  DevZoneWeb  |  SupportWeb
[ SystemLog ] [ not logged in ] [ Web: Imported ] goto:  options [ get info on or edit ] [ login or new user ] [ list of topics, hubs & nodes, or recent changes ]

Under construction :) -- JeroenVanGelderen, 4-mar-1998

Description

Event logging in JOS provides a standard, centralized way for applications (and the operating system) to record important software and hardware events. It also supplies a standard user interface for viewing the logs and a programming interface for examining the logs. Event logging provides a means to merge events from various sources into a single informative story. adapted from the MS API.

To provide a powerful, flexible SystemLog interface that combines the best features of Windows NT and UNIX logging.

Windows NT

Windows NT has three distinct log 'files': application, audit and system. The application log is used by 'user' applications, the system log is used by system services (aka daemons) and drivers. The audit log is used by both and contains all security related entries.

The application and system log support three log levels: info, warning and error.

The audit log is an oddball: it contains only audit succes and audit failure entries.

UN*X

Message Log - Levels

Code	Description and examples
LVL_ERROR	Errors. Example: configuration file missing, exiting.
LVL_WARNING	Warning messages. Example: configuration file missing, using defaults.
LVL_INFO	Informational messages. Examples: new SSH server-key generated.
LVL_DEBUG	Messages that contain information normally of use only when debugging a program.

Security Log - Levels

Code	Description and examples
LVL_SUCCESS	Audit succeeded.
LVL_FAILURE	Audit failed.

Content of these pages are owned and copyrighted by the poster.
Hosted by: