> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Michael Biebl > Sent: Friday, February 26, 2010 1:43 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 4.6.0 (v4-stable) released > > 2010/2/26 Rainer Gerhards <[email protected]>: > >> The problem is, that xconsole is running at this point! > >> To reiterate: > >> I start rsyslogd > >> then xconsole > >> then try to log a message > >> The result is the debug log and no message showing up in xconsole. > > > > that's what I am doing as well. I will try to record the session. > > Wait a sec. > With 4.4.2 (or any earlier version) I tried this: > start rsyslog > start xconsole > xconsole shows the last two log messages immediately > > With 4.6.0 the xconsole window is blank (which I guess made me believe > it blocked) > > With 4.6.0, I need to trigger a new log message (e.g. using logger > foo), and then xconsole will show a new message. > > So, xconsole does indeed show messages, but the behaviour is different > to 4.4 and earlier
Mhhh... I don't think it is worth preserving "backward compatibility" here. I think these two (just two!) messages were an artifact of the way files were written to pipes that nobody cares about. The old file writer was *very* suboptimal. If I would need to retain that old "functionality", I would need to remove almost all optimizations. So it would make more sense than to craft a new output module specifically for pipes. Not sure if this is granted by that "use case". I'd appreciate comments from the community at large. Thanks, Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
