Hi Helmut, Michael Biebl talked to me about the state of omprog. The problem is that it is not thouroughly tested. I created it in result to a feature request, but the original requestor lost interest. See here:
http://kb.monitorware.com/problem-to-migrate-from-syslog-ng-to-rsyslog-t8982. html So if you could give it a try, do some testing in your environment and let us know that it works well enough (or which bugs to fix), Michael will probably be happy to include it. I am hesitant to do this myself, as I have no real application for it and without at least one real life test, it is hard to judge how good a piece of software is... Rainer > -----Original Message----- > From: Helmut Grohne [mailto:hel...@subdivi.de] > Sent: Friday, October 23, 2009 1:29 PM > To: Debian Bug Tracking System > Subject: Bug#552095: rsyslog: please configure with --enable-omprog > > Package: rsyslog > Version: 4.4.1-1 > Severity: wishlist > Tags: patch > > Rsyslog provides a nice output plugin to forward logs to a program. > This > is already provided by logging to a named pipe in some way. However > logging to a named pipe has some drawbacks. When there is no reader > ready the pipe will not accept messages and messages are dropped. This > can happen when restarting the reader for instance. There also is > another plugin omshell already available. It however forks for each > line, which is not very effective. I therefore suggest adding > --enable-omprog to ./configure in debian/rules. > > Other solutions for reliably feeding log messages to a program are > welcome, of course. > > Helmut > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
