It was thus said that the Great [email protected] once stated: > On Tue, 12 Jul 2011, Sean Conner wrote: > > > Now, for the issue at hand. A minimum viable configuration (I think) > >would be to open "/dev/log" (or whatever the native logging socket it for a > >particular system) and to log *everything* to an equivalent of > >"/dev/console". End of story. No worries about stderr and upon boot-up or > >rsyslogd starting up, it would be noisy enough that someone might see > >something. > > the problem with this is that doing so can prevent an admin from being > able to fix the machine. > > it's _really_ hard to figure out what's wrong if you have the screen > scrolling as fast as it can spewing log entries at you.
Yes, and if started from the startup scripts, you lose stdout or stderr which makes it harder to diagnose. In this case, there *are* no good solutions so the tradeoff is: is silence better than the console being spammed? -spc _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
