On 9/22/06, Jeremy Henty <[EMAIL PROTECTED]> wrote:
LFS installs a fairly standard looking syslog.conf but doesn't explain its contents. I'm wondering if there is any justification for splitting the log messages to different files? There's so much to wade through you'll be using some log analysis/monitoring program anyway, so why not send everything to one file and process it in one go?
Doesn't it completely remove the functionality of the syslog to have everything dumped to one file? The entire point of syslog is that you can attach different meaning to the messages and have them filtered appropriately. In fact, I would argue that if you think that there's too much to wade through, you should create _more_ files and be _more_ selective in your filtering. Splitting the log into different priorities also allows permissions to be set, if so desired. Probably you don't want unprivileged users to see the authentication info. But maybe you could allow people in the mailadmin group to read mail.log. Those are my 2 cents. Of course, if you just want one file, you'll have the simplest syslog.conf around. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
