...

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.

use perm(-1) for those files.

ah, thank you! however, http://www.balabit.com/products/syslog_ng/reference/x354.html doesn't actually explain how to use them. for example, if i had a line: destination null { file("/dev/null"); }; where would i put the perm(-1) option? wherever i stick it, it seems to complain! thanks! 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