I wonder - would there be value to be able to see the returned data?

Maybe as an option to populate a macro with this data.  

Just thinking that there might be useful information coming back on the socket in some cases.

Jim

On Wed, May 10, 2017 at 2:54 AM, Balazs Scheidler <bazsi77@gmail.com> wrote:
Well, I can agree that this should be an option, but I didnt get around to implement this.

We actually process the input right now, but instead of simply terminating the connnection we should just read and ignore it.

On May 9, 2017 2:33 PM, "Fabien Wernli" <wernli@in2p3.fr> wrote:
Hi,

On Wed, Apr 12, 2017 at 10:04:34PM +0200, Balazs Scheidler wrote:
> Syslog-ng doesnt expect data on the socket on the reverse direction and
> shuts down the connection if anything is received.
>
> It is meant to work with /dev/log like devices.
>
> I was wondering if it's correct to ignore the reverse direction, is it?

Would you agree to change the behaviour?
I don't think it would break existing behaviour (only unexpectedly repair
things :))


______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq