> -----Original Message-----
> From: Chris Bartram [mailto:[log in to unmask]]
> Sent: Friday, October 08, 1999 8:28 AM
> To: [log in to unmask]
> Subject: syslog question
>
>
> I recently configured several laser printers to send their
> messages to one
> of our 3000s running syslog... Which I have configured to
> send all syslog
> messages to the system console.
>
> However, I'm seeing every message repeated 4 times. I suspect
> I'm confused
> re: syslog's configuration file. Here's what I'm using (syslog.conf):
>
> *.emerg         /dev/console
> *.alert         /dev/console
> *.crit          /dev/console
> *.err           /dev/console
> *.warning       /dev/console
> *.info          /dev/console
> *.debug         /dev/console
>
> My guess is I don't need all the above; can anyone clue me
> in? I just want all
> messages to go to the console (since we already monitor
> console messages).

Think of the urgency levels as an MPE outfence.  *.debug is equivalent to
outfence 0, and so that statement by itself is going to send *all* possible
syslog messages to your console.  The other 3 copies you're getting are
likely from *.info, *.warning, and *.err.  So you really just want "*.debug
/dev/console" if all you want to do is send everything once to the console.

I was good and explained the ordered nature of the urgency levels on my
Syslog/iX home page (http://www.bixby.org/mark/syslogix.html), but I
neglected to mention that if a message matches more than one configuration
statement, you will get more than one copy.

- Mark B.