On Tue, Jan 14, 2014 at 3:21 PM, Boylan, James <[email protected]>wrote:
> I can do that. Verified that it is in Fedora 20 ( > https://bugzilla.redhat.com/show_bug.cgi?id=998573). I'll have to look > into finding a place to install it. I'll probably just install a local VM > for it. > > I definitely agree that it might be prudent to create two different > implementation processes. One for the average user that is just looking to > install Rsyslog and the forwarding would work and the high end users who > require every little mhz of resources a system can provide. My hope is that > we'll be able to come up with a clean way of implementing this that doesn't > require a hack and can be done with a standard RPM install. > > I'll keep you in the loop of what I can find. > > excellent, thanks, much appreciated. Note that I will attend the European Fedora developer conference in about 3 weeks and I'll be able to talk to the RH package maintainer in person (we know each other for quite a while... and had quite some beers ;)). This may also bring up some good ideas (even though RH and Adiscon probably will end up with different views anyhow). Rainer > -- James > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Rainer Gerhards > Sent: Tuesday, January 14, 2014 8:14 AM > To: rsyslog-users > Subject: Re: [rsyslog] systemd without journal > > On Tue, Jan 14, 2014 at 3:10 PM, Boylan, James <[email protected] > >wrote: > > > I had a sneaking suspicion that would be the case. I might setup a > > system running the Fedora version with this setup (Fedora 20 I think?) > > when its available to do some tests on exactly how it is implemented > > and what possible options exist. That should help me be a bit ahead of > > the game for when it finally makes it's way into CentOS. > > > > > Oh, that would be great. I admit I was so busy the past month that I > didn't even bother to try this. As a side-note, I have some replacement > library work lying around that can be preloaded and redirects logging > traffic to a diffrent socket. It's hackish, but may be needed in high > performance environments. > > In any case, please keep us updated -- maybe we can craft some of the new > packages based on your findings. > > I really think we need two sets of standard things: one for the low end, > where folks are happy with the journal and just would like to get e.g. > router messages into it .... and one for real logging... > > IMHO both are valid use cases. > > 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. > _______________________________________________ > 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.
