> > > Reading project Lumberjack documentation[1], I spotted the > > > "SystemLogParseTrusted" parameter. > > > > > > From what I'm guessing, it will parses my messages trusted > > > properties and make them available as rainerscript variables. > > > At least, that's what I'm looking for. > > > > > > However : > > > - I can't find any documentation about it. > > > - Running a config check, rsyslog says that SystemLogParseTrusted is > > > an "invalid or yet-unknown config file command" > > > > > > I looked at imuxsock code, it's like the feature is implemented but > > > I can't find a way to use it. > > > > I just checked. Looks like this is contributed code where no doc was > > contributed. It seems to be supported via legacy parameters, only, so > > > > $SystemLogParseTrusted on > > > > should activate it. I'll see that I can fix these two nits when I have > > time to do > I was wrong. The v7 input param is "parsetrusted". So it is "just" the doc.
Actually, it was half-implemented. There was no way to activate it for the system log socket except via legacy config. I have now fixed this and also added doc. Patch is here: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=c469cff2f2e6cfd75ba91dfc106bed0baba99bf8 and will be released with upcoming versions. 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.
