redhat 7 has rsyslog-7.4.7. So no 8 for you :)
On Fri, Aug 8, 2014 at 10:58 PM, Jacob Steinberger < [email protected]> wrote: > It has to do with the slow machine that is enterprise. Big companies want > changes in a "dot" release to be minor, for them to not have to worry about > all their other applications, features and functions. > > Since RedHat (for example) adopted RSYSLOG v5 for their RHEL6 release, > they will likely never release anything before v5 for it. When RHEL7, or > higher, is released they'll look up upgrading packages to higher level. > It's the same with any program, MySQL, Net-SNMP ... > > Jacob > > > On 8/8/2014 12:01 PM, David Lang wrote: > >> As a sidenote, if you are 'stuck' running the old versions because >> that's what your OS supports, why aren't you asking your OS provider >> these sorts of support questions? >> >> If they can't answer you, then what is the benefit of sticking with the >> old version? >> >> David Lang >> >> On Fri, 8 Aug 2014, Bregant, Bob wrote: >> >> Having been in this situation before, I can confirm that v5 will only >>> support multiple rulesets on RELP if you run separate rsyslog >>> processes with separate configs for each ruleset (putting only the >>> listeners that need to use that ruleset in each config). >>> >>> Support was added in 8.3(.2?) to allow the kind of imrelp per-listener >>> ruleset binding that you're asking for. The newer versions really have >>> done major improvements, and they're not that hard to handle if you >>> use the pre-built packages. >>> >>> Hope that helps. >>> >>> On Aug 7, 2014 6:37 PM, David Lang <[email protected]> wrote: >>> On Thu, 7 Aug 2014, Ivan Lezhnjov IV wrote: >>> >>> Hello, >>>> >>>> Another question I had was, whether imrelp supports ruleset/input >>>> binding like imtcp does? I run a legacy v5 which is still the default >>>> with major Linux distributions like Ubuntu so I'd like to stick with >>>> this version… just because it's a default. >>>> >>> >>> that's a very old version, you'd have to dig in the code >>> >>> Anyway, what I have in mind is this, seemingly, common approach: >>>> >>>> $RuleSet remote >>>> >>>> … >>>> >>>> $InputTCPServerBindRuleset remote >>>> $InputTCPServerRun 2514 >>>> >>> >>> this wouldn't do relp, it would do normal tcp right? >>> >>> In my setup, I use rulesets to split local and remote logging. I'd >>>> love to user RELP over TCP, but I don't see how if I want to preserve >>>> the configuration where local and remote messages are stored in >>>> separate files. >>>> >>> >>> you can do filtering based on fromhost-ip, if it's from 127.0.0.1 send >>> it to one >>> ruleset, else send it to another one. >>> >>> David Lang >>> >>> Is there any way to do it with RELP using rulesets, or do I need to >>>> use an entirely different approach? >>>> >>>> Ivan >>>> _______________________________________________ >>>> 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. >>> >>> >> >> _______________________________________________ >> 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. > _______________________________________________ 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.
