Hi! I have a problem with syslog-ng running in chroot: Nov 17 15:45:02 burp /USR/SBIN/CRON[26238]: ... Nov 17 14:47:42 burp syslog-ng[16074]: syslog-ng version 1.6.4 going down Nov 17 14:47:47 burp syslog-ng[26331]: syslog-ng version 1.6.4 starting Nov 17 14:47:47 burp syslog-ng[26331]: io.c: do_read: read() failed (errno 1), Operation not permitted Nov 17 14:48:27 burp syslog-ng[26331]: syslog-ng version 1.6.4 going down It seems that all messages that are generated internally within syslog-ng are logged with false timstamps. The system is debian testing. I am testing syslog-ng in chroot before deploying it on our production syslog server. :) Good thing I did this test. The second start in the log snippet was done by hand. Not from the init script. I am also interested to know what that io.c message is. It does not seem to affect syslog-ng. I had another problem: when logrotate rotated the logs the sent a reload to the chrooted syslog-ng process, it kept the syslog open. So after that was deleted it kept happily logging there not into the newly created file. I works just fine if I send restart instead of reload. Thanks in advance. g.