> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Michael Biebl > Sent: Monday, March 01, 2010 12:01 AM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 4.6.0 (v4-stable) released > > 2010/2/28 Rainer Gerhards <[email protected]>: > >> OK, rather than trying to figure out what may be going on here, I'll > >> see that > >> I copy the old omfile code and create a new ompipe. So that will > behave > >> exactly like it did before. The new optimizations are not so > important > >> for > >> pipes. > > > > I have done this now. I would appreciate if you could checkout the > v4-stable > > git head and try with that one. It should now have the exact same > behavior as > > in 4.4.2 (the pipe code is now the same!). I tested on Debian and it > worked > > like before. > > I use $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat > in my rsyslog.conf, but the new ompipe module does not seem to respect > that setting but always uses the high-resolution time format.
I see - that was a side-effect that pipes used the same output module like regular pipes. But I have now re-established it, please try the newest git v4-stable branch. > > Other than that, I did not (yet) experience any blank xconsole windows > with v4.6.0-5-gf12a199 (git describe) > > Just curious, when I fire up xconsole after boot, I get two log > messages immediately. Where do those log messages come from? It seems to stem back to the API usage in the old code. The old code opens the pipe and tries to write. It disables writing only when the API returns it would block. The new code used create() instead of open, and that immediately returned an error if nobody was listening. It looks like with the old sequence, the OS permits to write a handful of bytes before it returns EAGAIN. However, I would not take that behavior for granted: I guess it may be different under different platforms and/or versions. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
