>>> +1 - rsyslog is already much more scalable than most other log >>> collectors. Why "especially no imjournal"? >> >> >> As per a discussion here a couple months ago, adding imjournal more than >> doubles the memory footprint of a running rsyslog instance, even if it's not >> used. > > > Then can it be made a dynamically loadable module? Same with every module - > is there a way to build them and provide them so that they are not part of > the base rsyslog executable/library?
That's what they are. If you don't load a module, it'll have no footprint. I think David was refering to that we often simply need imjournal to get hold of the regular syslog. For a file content shipper, that's totally unnecessary. 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.
