2015-03-03 12:58 GMT+01:00 Thomas D. <[email protected]>: > Hi, > > here's the output with rsyslog.out.log: > > FAIL: imuxsock_logger.sh > ======================== > > [imuxsock_logger.sh]: test imuxsock > rsyslogd started with pid 12030 > imdiag[13500]: mainqueue empty > rsyslog.out.log ./resultdata/imuxsock_logger.log differ: byte 2, line 1 > imuxsock_logger.sh failed > contents of rsyslog.out.log: > " 2015-03-03T12:52:51.695966+0100 vm-gentoo-x64 root - [timeQuality > tzKnown="1" isSynced="1" syncAccuracy="266016"] test" >
OK, that clarifies. While it is nice to see a RFC5424 header on the local log socket, imuxsock does not support this. However, this is not new, it is so for quite some years (as a result of pre-journal systemd integration, I think back in v5 days). So this should not be a new fail. I guess the test was not run for some reason, maybe it was among a set I added. Of course, it would make sense to enhance imuxsock to support multiple formats. The question is if that really makes sense. In spit of the recent movement towards journal and the trend to replace imuxsock by imjournal on such systems, I think the days of this module are more or less over. At least as a short-term measure we should disable this test for Gentoo, I just need to see how I can do that. Do you know how to check for Gento inside the testbench scripts? FAIL imuxsock_logger.sh (exit status: 1) > > ...and imuxsock_logger.log from this run is still > > # cat tests/resultdata/imuxsock_logger.log > test > > That's a canned file to compare the run against. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
