Log on as mgr.syslog.
Examine syslog.conf
and customize for your own environment.
:stream JSYSLOGD.PUB.SYSLOG.
Stop Syslog/iX by issuing the command :ABORTJOB.##
## ## :TELL @.@ ## *.emerg * ## ## Write to the :CONSOLE ## *.alert /dev/console ## ## :TELL @.SYSLOG ## *.crit @.SYSLOG ## ## :TELL MANAGER.SYS ## *.err MANAGER.SYS ## ## Forward to syslogd on another host via UDP ## *.warning @some.host.running.syslogd ## ## Write to the :CONSOLE *.info /dev/console ## ## Write to a file ## *.debug /tmp/syslog.log |
The messages coming from a program are classified into critical
informative, alert, error,
emergency etc. The syslog configuration file
tells the syslog daemon how to post these messages. They could be
sent to the console or to a log file, a printer, a message sent
to an administrator or to another machine. SYSLOG uses UDP to send
to another machine.
Explanation of parameters in syslog configuration file:
Syslog has a set of parameters that can be configured. Messages
are classified into several levels. These messages can be directed
to different outputs like console, logfile and so forth. They can
also be sent to another machine which runs a syslog daemon.
They are classified as follows:
debug
info
error
critical
warning
alert
emergency
Now these messages could also be sent to a particular user
by using the "tell" option followed by the user
name.
They can also be sent to another machine by using "@machine name".