In some mail from Tina Bird, sie said: > > Don't you all love it when I'm revamping my class? > > 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? Because then it wouldn't be an obscure app requiring black art unix wizardry to master! :-) I imagine it's one of those applications that dates back to when most of your class was in nappies (if that!) and computer programming was much more minimalistic than it is today. On top of that, syslogd generally "works" so there's rarely an occasion or cause to go introduce NEW functionality, even if it is just enhanced error messages. Afterall, EVERYONE who's editing it knows the rules, right ? The best thing about its parsing is that it is at odds with how emacs writes out white spaces :-) Darren _______________________________________________ LogAnalysis mailing list LogAnalysisat_private http://lists.shmoo.com/mailman/listinfo/loganalysis
This archive was generated by hypermail 2b30 : Wed May 07 2003 - 01:52:40 PDT