[syslog-ng] /dev/log/ recreated when reloading syslog-ng?

I've been investigating a problem with rbldnsd - when syslog-ng is reloaded (via logrotate), the /dev/log device is reopened/recreated, which causes a chrooted rbldnsd to lose touch and essentially stop logging. It was suggested to me to create a /dev/log inside the rnbldsdn chroot jail, but that seems sub-optimal. Is syslog-ngs behaviour correct? /Per Jessen, Zürich