Be sure to read the "RKT couplings" below for additional information and updates to this entry.
|Subject: (7.17) What's a decent syslog.conf configuration?|
The configuration will be different for each site, but here is what
Greg Earle recommends as the lines for the "news.*" related part.
Remember that most syslog's require tabs, not spaces.
Greg's canonical SunOS 4.1.x INN-related syslog.conf entries (which can
be merged into your current configuration):
# # INN stuff # ## Send critical messages to everyone who is logged in and to the console. news.crit * news.crit /dev/console ## Log news messages to separate files. ## Note that each level includes all of the above it. ## =()<news.crit @<_PATH_MOST_LOGS>@/news.crit>()= news.crit /var/log/news/news.crit ## =()<news.err @<_PATH_MOST_LOGS>@/news.err>()= news.err /var/log/news/news.err ## =()<news.notice @<_PATH_MOST_LOGS>@/news.notice>()= news.notice /var/log/news/news.noticeIf you don't want /var/log/messages to be crowded by messages from news
add the following to the line, where /var/log/messages get logged:
news.none so that the line reads (as an example):
*.err;kern.debug;auth.notice;mail.crit,news.none /dev/consoleOn some systems you can add a flag to some entries in order to instruct
syslog not to sync after each write. This might help raising throughput.
Or else move the logs from busy file systems if that flag is not
[Last Changed: $Date: 1997/09/16 01:25:57 $ $Revision: 2.25 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]