2. Speeding up syslog
● Filter the messages at the source
● Letting syslog filter out your messages
according to various parameters
● Have a separate hard drive just for logging (to
avoid IO pressure on the main one)
● Telling syslog to put your log messages in
RAM instead of permanent storage
3. Putting syslog output in RAM
● It usually OK for many many systems out there
● Does not add to the load on the IO system (you
don't usually have a spare drive)
● Makes syslog perform much faster in a log of
the synchronous implementations of syslog out
there
● Should be rotated or removed from time to
time, ofcourse
6. Logging from the command line
● Use the logger(1) utility
● Part of the bsdutils package
● Example: logger hello
● Many options to control priority, tag, socket,
process id logging and more
● Good for scripts and languages that do not
have a more integrated API to syslog
7. Logging from the command line
● Use the logger(1) utility
● Part of the bsdutils package
● Example: logger hello
● Many options to control priority, tag, socket,
process id logging and more
● Good for scripts and languages that do not
have a more integrated API to syslog
Editor's Notes
This slide show is about logging in linux It will survey and compare the various syslog implementations. It will survey and compare the various logging library APIs. It will show how to log to syslog from various languages (perl, python, C/C++, ruby, shell, and more)
