2013/6/19 Rainer Gerhards <[email protected]>
> On Wed, Jun 19, 2013 at 2:48 PM, Radu Gheorghe <[email protected] > >wrote: > > > Hi Risto, > > > > Yes, I've used omprog and it's a good temporary solution :) There are two > > things I've bumped into: > > - performance. If you can develop (or pay Adiscon to develop) a rsyslog > > output plugin that can do what your external program does, it will > probably > > be way faster. Because it can make use of rsyslog's features, like having > > multiple threads or processing logs in batches > > > > I guess Risto will run some input to SEC - am I right here? > > > > - reliability. omprog will restart your external program if it goes down > > for any reason. But your external program needs to ingest messages > quickly, > > otherwise the pipe will get full (and it's 4-64K, it's not clear to me. > > Tiny, anyway). At that point you will lose messages. > > > > > I have just checked the code and that is not intentional. I may have > overlooked something, as omprog was originally writen to a user request, > but that users disappeared when it was done and nobody else reported much > on it. I think this is the right solution for external programs, and so I > would be very happy to look into problems that the module may have. > > I might have spoken ahead of myself (or rather, out of old memories) about losing messages. Because I don't actually know what is used for communication. I guess a test can easily reveal whether it loses messages or not. _______________________________________________ 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.
