Hi, I've merged this bug with the (meanwhile closed) rsyslog bug mentioned by Jim Barber.
So this issue should be fixed in rsyslog 5.7.4-2. Regards Hannes -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
