P. 1
TEC Implementation Examples Sg245216

TEC Implementation Examples Sg245216

|Views: 1|Likes:
Published by bupbechanh

More info:

Published by: bupbechanh on May 25, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





UNIX provides two applications where an error or warning message is logged.The
first method provided is the function syslog; the second method is the error
reporting program.

The syslog relies on a process called syslogd.This process will report operating
system conditions to the system console or to a specific logfile.

Messages are tagged with codes indicating the classification of the message.A
classification, known in UNIX as a priority, is encoded as a facility, which describes
the component of the system generating the message, and as a level, which
indicates the severity of the message.

The logger command, found in the /usr/bin directory, provides an easy-to-use
interface to the syslog subroutine.A message variable can be specified on the
command line, which is logged immediately, or a file variable is read and each line
of the file variable is logged.

The logfile adapter connects to the syslogd daemon by adding an entry to the file
/etc/syslog.conf file.This file controls the output of the syslog daemon.It supports
subscriptions by other AIX processes to specific subsets of messages handled by
the syslog daemon.Each entry in the file consists of two parts; a selector, which
determines the messages of interest to the subscribing process, and a destination
file to which the selected messages are directed.The selection of messages is
based upon two criteria: the facility generating the message and the priority of the
message.The facilities supported are:

kern - Kernel

user - User level

mail - Mail subsystem

daemon - System daemons

auth - Security or authorization

syslog - Syslogd daemon

lpr - Line printer subsystem

news - News subsystem

uucp - UUCP subsystem

* - (All facilities)

The priority levels that can be selected are:

emerg - Emergency messages (LOG_EMERG) such as fixed-disk errors.

alert - Important messages (LOG_ALERT) such as serious hardware errors.

104TEC Implementation Examples

crit - Critical messages not classified as errors (LOG_CRIT), such as improper
login attempts.

err - Messages that represent error conditions (LOG_ERR) such as an
unsuccessful disk write.

warning - Messages for abnormal, but recoverable, conditions

notice - Informational messages.All messages without a priority designation
are mapped into this priority messages (LOG_NOTICE).

info - Less significant informational messages (LOG_INFO).

debug - Debugging messages (LOG_DEBUG).

none - Excludes the selected facility.

Destinations may be specified as follows:

/Filename - Full path name of file opened in append mode.

@Host - Host name.

User - User name(s).

The default entries created by the logfile adapter install process are shown below:

# Tivoli logfile adapter entry, ID=default
.emerg; .alert; .crit; .err; .warning; .notice; .info
/tmp/.tivoli/.tecad_logfile.fifo.rs6 28.default
# End of logfile adapter entry, ID=default

This entry directs the syslogd daemon to pass all messages to the specific file for
the logfile adapter in /tmp.

The refresh command would normally be used to stop and restart syslogd after
updating of the syslog.conf file.However, when the logfile adapter process is
running the refresh command should not be used.Use the init.tecad_logfile script
instead.In our case, it was located in:


There may be a performance benefit in tailoring the logfile adapter entry to indicate
that only messages from specific facilities or message-specific priority levels get
passed to the adapter.In addition, these entries should be reviewed to make sure
that all of the messages you are expecting to be passed by the event adapter
actually appear at the event server.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->