Sorry, I should have been a bit more clear... On Tue, Jul 12, 2011 at 3:16 AM, Rainer Gerhards <[email protected]> wrote: > Aaron, sorry, definitely my fault, but I don't get you here. Are you saying a > fallback is good/required -- or not? As I just wrote in reply to David, I'll > probably make it stderr-and-exit today, but am very open to other > suggestions.
I like stderr-and-exit - and prefer it for my use case. That being said, I think it should probably be a compile-time option. There are use cases, like in generic out of the box distros, where a badly configured syslog should still come up - since its somewhat essential to discovering other possible issues on the machine. The problem is most of us here use syslog beyond the generic host logging that a large majority of people use it for. I think a compile-time option to stderr and exit out is probably the best of both worlds. -Aaron _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
