Pls open a bug report on github so i remember when i am back. Sent from phone, thus brief. Am 31.07.2014 19:12 schrieb "Jacob Steinberger" <[email protected] >:
> On 7/31/2014 11:51 AM, Rainer Gerhards wrote: > >> On Thu, Jul 31, 2014 at 6:48 PM, Jacob Steinberger < >> [email protected]> wrote: >> >> After 6 months I got the "OK" to install the newest version of Rsyslog. >>> Much cheering occurred. >>> >>> I'm trying to build a new configuration file using all the new snazzy >>> methods and I'm having trouble with stock operating system features. UDP >>> reception, MySQL logging aren't causing me any problems. >>> >>> module(load="imuxsock" ruleset="kernel") >>> module(load="imklog" ruleset="kernel") >>> >>> ruleset(name="kernel") { >>> # lots of if prifilt with action omfiles >>> } >>> >>> Before I get too far here, in the legacy configurations you didn't have >>> to >>> specify which klog or socket to bind to for the default operating system >>> messages, do we need to do that now? >>> >> >> >> No >> >> >> Assuming no, is the ruleset call in module() supported - I couldn't find >>> anything in the documentation about generic commands supported by >>> module() >>> or with regards to imklog or imuxsock. >>> >>> >> If the doc does not list it, then it's not possible. In general, the new >> conf expects that all inputs are defined via the input() statement, but as >> you say, some of the old modules have some legacy. A work-around is to >> define the OS input via input() as well -- or simply use the default >> ruleset just for that input and define other rulesets for the more >> "regular" inputs. >> >> It's a good question, I wonder it didn't come up earlier. It may make >> sense >> to add a feature request, just be aware that I am heading for vacation and >> so it will take some extra time... >> >> HTH >> Rainer >> > > Bit more tinkering done, looks like it's going to need work. > > module(load="imuxsock" ruleset="kernel") -- generates error, unknown > option ruleset > input(type="imuxsock" ruleset="kernel") -- generates error about no > socket, and unknown option ruleset > input(type="imklog" ruleset="kernel") -- generates error that imklog > doesn't support "input" > > I'll go the default ruleset path. > > Jacob > _______________________________________________ > 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.
