> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Michael Biebl > Sent: Sunday, February 28, 2010 2:16 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 4.6.0 (v4-stable) released > > 2010/2/26 Michael Biebl <[email protected]>: > > 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 > > Hm, it just happened again. > I rebooted my system, logged into my system, ran "sudo xconsole", > "logger foo", but nothing shows up in the xconsole window. > > I then killed xconsole, restarted rsyslog, ran "sudo xconsole" again, > "logger foo" and this time it works. > > Weird. There is definitely something fishy here.
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. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
