> > I just verified the case. I get the failure if xconsole is not > active, what > > is perfectly OK IMHO (because otherwise it would block on the pipe). > As soon > > as I start xconsole, everything works fine and messages are displayed > in > > xconsole. When I stop xconsole I get "broken pipe" errors and if I > restart it > > everything works again. > > > > So I do not see an issue. I tested on Debian lenny with all current > updates > > applied. > > hm, it's perfectly reproducible here.
also on Debian lenny? Anything else I could do to set up my environment so that the problem occurs? > starting rsyslogd, then xconsole, will cause xconsole to hang and no > message is written to the xconsole window. > 4.4.2 did not behave that way. > > See also the debug log I sent previously The log tells me that it has a problem to write to the pipe, and thus ignores it. This also happens at my system, but only if xconsole is not running. So the debug log does no help very much this time. > Is there anything else I can do to help you debug this? When I get the platform information from you, I will see if I can record a session in my lab. Maybe you see that I do things differently from you. One thing I notice is that xconsole seems to be unable to access /dev/xconsole if I start it as non-root, thus resulting in no listener on the pipe and thus the error appears in rsyslog. However, this is not rsyslog-related, but I guess these permissions are set by xconsole. After all, there should be no change to 4.4.2 (and I don't see any difference in that regard to 4.4.2 on my system). Rainer > > Michael > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > _______________________________________________ > 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
