Re: [hpoj-devel] lots of ptal-mlcd fixes

[Obi-Wan <bv...@in...>]

>> I also wouldn't mind having it log to the lpr facility 
>> instead of daemon
>> or whatever, since that seems like the most appropriate place.  Others
>> may disagree.
>
> What difference does that make?  Does it cause the messages to get logged
> into a different file (according to rules in /etc/syslog.conf)?  The message
> itself doesn't actually reflect the facility, and it seems to me that
> /var/log/messages is an appropriate file to log into, since that's where the
> kernel messages go (useful for debugging USB plug/unplug issues).

With the stock syslog, splitting into different files is done based
on the facility and the log level, as specified in your /etc/syslog.conf
file.

I guess I feel like I'd rather have all my printer-related messages
going to the same spot.  LOG_DAEMON is more of a generic catch-all
facility for use by miscellaneous daemons that don't have their own
pre-defined facility and don't want to use one of the eight local
facilities.  Basically, everything except mail, printing, uucp,
usenet, and cron.  Lprng & its cousins all log to LOG_LPR, so it
makes sense that the low-level printer drivers log there as well.

Does anyone else care one way or the other about this?  If it's just
me vs the world, I'll shut up.  I've been a professional Unix sysadmin
for about a decade, and one of my pet peeves (especially recently,
but not due to this project) is programs that put their logs where
you'd never expect to find them.  For instance, TCP Wrappers by
default logs to the LOG_MAIL facility.  What the ????  The first
thing I do when I build it on a new machine is change the source
to LOG_LOCAL1 so I can separate the tcpd messages into their own file.
</rant>

-- 
Ben "Obi-Wan" Hollingsworth                             ob...@je...
   The stuff of earth competes for the allegiance I owe only to the
     Giver of all good things, so if I stand, let me stand on the
       promise that You will pull me through.  -- Rich Mullins