The SCOadmin event log
SCOadmin includes a logging facility to record administrative events,
including errors and object creation, among others.
SCOadmin events are recorded along with other system events
in /var/adm/syslog. These events help you keep track
of all modifications made to your system configuration.
NOTE:
Do not confuse messages contained in the SCOadmin event log
with the system error messages located in /var/adm/log/osmlog.
See also:
Understanding the SCOadmin event log
All SCOadmin managers generate records of
administrative events that occur during the daily operation
of your system. By default, SCOadmin errors are the only events
recorded. This allows you to monitor any problems that might occur.
You can also elect to record all administrative changes made to the
system, for example when a user account is added to the system or
modified.
Log entries use this format:
date sysname syslog SCOADM:
sessionID object instance event_type message
Where:
sysname-
name of the host system
sessionID-
tty for the login session when the event took place
object-
type of object
instance-
name of object
event_type-
event type
message-
the system message associated with the event
Here is an example:
Jul 12 22:27:38 apathy syslog: SCOADM: localhost {sco_printer}
{toaster1} objectCreation SCO_OFACE_MSG_OBJECT_CREATION {object
creation {(null)}}
The event types are:
Object creation-
the creation of an object, such as a new printer
Object deletion-
the deletion of an object, such as a printer
Attribute change-
the modification of an object, such as the configuration
values for a printer
Error-
a failure to complete a requested action,
typically called an error message
Warning-
an action was completed successfully, but with a problem
Notice-
an informative message
You can modify the list of event types by editing the
/usr/lib/scoadmin/registry/events file.
Using the SCOadmin event log
You can select events to be logged using the
Options Log Options
selection in the SCOadmin launcher. It displays the
events currently logged and not logged.
-
To log an event, highlight it in the ``Ignored Events''
column and click on the Log event button.
-
To ignore an event, highlight it in the ``Logged Events''
column and click on the Ignore event button.
See also:
Previous topic:
SCOadmin error trace
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004