On Mon, Jan 27, 2014 at 10:41 PM, Assaf Gordon <[email protected]> wrote:
> Hello, > > > On 01/27/2014 09:42 AM, Rainer Gerhards wrote: > >> I have a hard time finding out why I can't redirect Python's stdout to >> rsyslog's omprog, while it works for stderr. Details are here: >> >> https://github.com/rsyslog/rsyslog/issues/22 >> >> I would deeply appreciate if someone could offer advise. It's probably >> something trivial that I am overlooking, but ... I am overlooking it ;) >> > > While I do not know the details of the python program, but the first > things that pops into mind when dealing with STDOUT vs STDERR piping is > line buffering. > I'm certain Python's STDOUT is highly buffered, whereas STDERR is either > line-buffered or unbufffered. > > it looks like you nailed it! The problem seems to go away after a flush :-) Thanks, Rainer > The first thing I'd try is one of these: > http://stackoverflow.com/questions/107705/python-output-buffering > > HTH, > -gordon > > > _______________________________________________ > 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.
