And if you don't know this already, this doc may be useful: http://download.rsyslog.com/design.pdf
It is not totally up to date, but covers the most important ides (most importantly the engine state transitions). Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Rainer Gerhards > Sent: Friday, July 30, 2010 8:45 AM > To: rsyslog-users > Subject: Re: [rsyslog] Buggy pipe behaviour > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Steffen Sledz > > Sent: Friday, July 30, 2010 8:30 AM > > To: rsyslog-users > > Subject: Re: [rsyslog] Buggy pipe behaviour > > > > Am 30.07.2010 08:26, schrieb Rainer Gerhards: > > > Interesting -- I don't see any reprobing of the output. > > > Unfortunately, the debug output does not really provide > > > much insight of what is going on at the moment. I'll see > > > if I can add some more instrumentation to try track this > > > down. Not sure if I can do this today. > > > > Can you give some hints which source files/functions are primarily > > involved here? May be we can do a little code review. > > I'd start with ./action.[ch] and obviously ompipe itself. It may be > useful to > see what/how ompipe returns. You can also set debug mode to do a > function > trace (see debug doc), this requires --enable-rtinst. > > Rainer > > > > Steffen > > > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
