On Fri, Jul 5, 2013 at 12:44 PM, Schmidauer Martin <[email protected]>wrote:
> > > What do you want me to do exactly? > > it is best to run rsyslog interactively. You can then simply say - in a > terminal > > window: > > $ valgrind /path/to/rsyslogd -n ...regular options-- 2> valgrind.log > > > You need to > > > > $ kill rsyslog-pid > > There are some errors. See attachment. > > thx, will check. In the meantime I have added some better error messages. You can either build vom v7-stable git master branch or apply this patch: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=d43a2e8f3f0e1f87bfa041263f02d727c00e97c7 Please privately send me a debug log. I'll have a look at valgrind now. Rainer > Martin > > _______________________________________________ > 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. > _______________________________________________ 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.
