On Thu, 28 Apr 2011, Rainer Gerhards wrote:
-----Original Message-----
From: [email protected] [mailto:rsyslog-
[email protected]] On Behalf Of [email protected]
my point is that insead of figuring out what effect all the loaded
modules have, how to apply all the modifiers in order, etc. just throw
out all of the existing config and start the new config clean from
scratch, but do it in a separate process so that the existing one can
keep processing the logs it's already received.
That bad thing is that this doesn't work for existing TCP connections. Of
course you can start processing new connections with the "new" instance, but
that means that new data coming in via old connections - even hours later -
would still be processed by the old config.
wouldn't a fork duplicate all the file descripters? then the old copy
would close it's copy of the file descripters and the new copy would start
using them (you would have to time this transition for when the old copy
has finished reading a message so you don't make the transition in the
middle of a message)
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
