Subject: (no subject)
From: wesley.craig@umich.edu
Date: Thu Jan 13 1994 - 14:29:39 EST
> From: howie@warlok.ds.boeing.com (Howard Modell)
> To: netatalk-admins@umich.edu
> I'm getting A LOT of
> messages out atalkd, and they clutter /var/adm/messages and console
> Jan 10 14:54:17 warlok atalkd[3009]: route: 21856 -> 19065.1: File exists
> .... which mostly shows up during boot-up/initialization, and ..
"File exists" means "route exists", when applied to routing. It sounds
like you've restarted atalkd without rebooting the machine. While this
usually works ok, it *does* produce a lot of messages, and is certainly
not something I suggest doing.
> Jan 10 22:42:30 warlok atalkd[3009]: route: 8438 -> 19065.1: No such process
> ... which shows up seemingly 'randomly' during the day ..
"No such process" means "no such route". One could call this a bug in
atalkd. atalkd doesn't keep track of whether or not there is a kernel
route associated with an entry in its in-core routing table. When
routes go bad, it will sometimes remove the route from the kernel
twice.
> Is there anyway for me to turn those messages off, or send them to
> /dev/null?
Just in general, anyone using netatalk would do well to understand
syslog. As an example, here's the syslog.conf on our main server,
terminator:
--- cut ---
daemon.debug /var/log/daemon
mail.info /var/log/mail
news.info /var/log/news
local2.info /var/log/named
*.emerg /var/log/emerg
*.alert /var/log/alert
*.crit;mail.none /var/log/crit
*.err;news.none;local2.none;mail.none /var/log/err
*.warning;local1.none;local2.none;news.none;mail.none /var/log/warning
*.info;news.none;mail.none;daemon.none;local0.none;local1.none;local2.none /var/log/info
lpr.debug;news.none;mail.none;daemon.none;local0.none;local1.none;local2.none /var/adm/lpd-errs
--- cut ---
Along with this, we run a script called "newsyslog" just before
midnight, every day. It cycles the log files, so we have
/var/log/err.Wed, etc, parses some number of the logs, posts statistics
to one of our local news groups, and restarts syslogd.
--- cut ---
#!/bin/sh
#----------------------------------------------------
# save a week's worth of logs.
#----------------------------------------------------
PATH=:/bin:/usr/bin:/usr/ucb
DAY=`date +%a`
LOGDIR=/var/log
cd $LOGDIR
for I in `ls | grep -v "\."` ; do
cp $I $I.$DAY
cp /dev/null $I
done
#-----------------------------------------------------------------------------
# mail the news stats
# innlog.awk is a set of specific stats, including who is reading what
# innlog.awk2 gives more general stats
#-----------------------------------------------------------------------------
export DAY
su news -c "/bin/awk -f /usr/local/news/lib/innlog.awk /var/log/news.$DAY | mail usenet"
su news -c "/bin/awk -f /usr/local/news/lib/innlog.awk3 /var/log/news.$DAY | mail -s NewsNews umich-itd-stats"
kill -HUP `cat /etc/syslog.pid`
--- cut ---
The syslogd man page is also pretty enlightening. Sadly, people
running on Ultrix machines don't really have anything like this.
:wes
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:20:47 EST