Re: [logs] tbird rant: syslog.conf, tabs and spaces

Previous message: Kevin W. Gagel: "Re: [logs] IIS Message Meanings"
In reply to: Tina Bird: "[logs] tbird rant: syslog.conf, tabs and spaces"
Next in thread: Darren Reed: "Re: [logs] tbird rant: syslog.conf, tabs and spaces"
Reply: Darren Reed: "Re: [logs] tbird rant: syslog.conf, tabs and spaces"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

robat_private

At 03:57 PM 5/6/2003, Tina Bird wrote:

>Surely one of the most common errors for newbies configuring syslog is to
>use blank spaces instead of tabs in syslog.conf.  When that happens,
>syslog variously fails to start because it can't parse the file, or starts
>but refuses to accept any data.
>
>Why the *bleep* can't it be civilized and write a message to the damn
>system log?  Or to the console? Or to its own special logfile?

My biggest pet peeve about traditional syslog daemons is that if the system 
admin (me, usually) forgets to actually create the target file called out 
in a syslog rule then syslog will only tell you about it at start time 
rather than simply create the file in question.  I admit that a truly 
paranoid and control oriented admin may not wish a system utility like this 
to go about creating files.  However, I've always felt that if syslog can 
detect that I haven't created a target log file why shouldn't it just go 
ahead and create the fritzing thing rather than just whining about it.

Cheers.
Rob

              It's never too late to have a happy childhood.
                    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                     Rob Scott, mailto:robat_private
        Langley, Washington on Whidbey Island (a suburb with a moat)

_______________________________________________
LogAnalysis mailing list
LogAnalysisat_private
http://lists.shmoo.com/mailman/listinfo/loganalysis