On 16/08/10 10:22, Fekete Robert wrote: > > I've confirmed it with the developers, it's a syslog-ng bug. > > Robert Thanks for the bug confirmation Robert - best not to depend on the current behaviour then :)