ever since i upgraded to syslog-ng 1.6.0rc3 from 1.4.14, when syslog-ng is restarted something wierd happens. I get 3 error messages: Sep 29 11:56:47 proxy syslog-ng[1614]: Changing permissions on special file /dev/xconsole Sep 29 11:56:47 proxy syslog-ng[1614]: Changing permissions on special file /dev/tty10 Sep 29 11:56:47 proxy syslog-ng[1614]: Changing permissions on special file /dev/null in particular, it changes /dev/null to rw access for root only. q1: why does it do this? and q2: how to i stop it? everytime i restart syslog-ng i have to chmod the /dev/null file or squid goes nuts and spawns off loads of its own processes, which eventually hangs the machine. all 3 files are referenced in /etc/syslog-ng.conf as destinations. if syslog-ng has access to the files (i chmod /dev/null to 666), why should it change the permissions to block other programs? i am running this on SuSE 8.0. thank you! chris -- The content of this e-mail is confidential, may contain privileged material and is intended solely for the recipient(s) named above. If you receive this in error, please notify Software AG immediately and delete this e-mail. Software AG (UK) Limited Registered in England & Wales 1310740 Registered Office: Hudson House, Hudson Way, Pride Park, Derby DE24 8HS