Am 29.07.2010 10:46, schrieb Rainer Gerhards: > This sounds like intended behavior. When an action fails (pipe fails when > nobody reads and it is tried to write to it), rsyslog retries the configured > number of times and then suspends the action for the configured period (at > least I think it is configurable, you need to look up the details). Only > after this period the action is retried. If it fails again, it is > re-suspended, but this time with a longer suspension period. This is done so > that rsyslog does not spent a lot of time on actions known to be failing.
So you say, if i wait long enough the messages should receive the end of the pipe? Are there some related debug printouts i can search for? Can you give some hints to the related configuration parameters (URL or keyword). Unfortunately the manual is not very helpful here. > From what you wrote, I think your use case would probably better be served by > omprog, but I may be wrong. If you think about this route, you need to know > that someone requested the functionality, but was never seen when it was done > ;) So the module is only barely tested. Same wish. Where can i read more about omprog? Regards, Steffen _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
