You could also create another /dev/null for syslog to use..
ls -lL /dev/null crw------- 1 root root 1, 3 Apr 11 2002 /dev/null major^ ^minor mknod usage: mknod name [ b/c major minor ] [ p ] mknod /dev/null.syslog-ng c 1 3
The major/minor numbers will vary from Unix to Unix. (i.e. Solaris is 13 and 2) Brian -----Original Message----- From: Brian E. Seppanen [mailto:seppy@chartermi.net] Sent: Tuesday, February 04, 2003 2:32 PM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]Changing Permissions on /dev/null On Tue, 4 Feb 2003, Nate Campi wrote:
On Tue, Feb 04, 2003 at 01:09:39PM -0500, Brian E. Seppanen wrote:
Hi Folks:
I've just installed 1.5.26 and for some reason I get the following errors Feb 4 12:23:01 host syslog-ng[15522]: Changing permissions on special file /dev/null
permissions are then listed as crw------- 1 root root 1, 3 Apr 11 2002 /dev/null
cronjobs that redirect output to dev null for ordinary admin accounts are failing because they no longer have permissions to write to /dev/null
When did syslog-ng start changing the permissions on /dev/null, so what release do I need to backpeddle to.
You need to modify your syslog-ng conf file to not use /dev/null as a destination.
Is there some way to have it leave the permissions of /dev/null as it previously was? I toss messages for a page queue run that is done every 10 seconds. I don't want to drown in those messages, and I don't want to waste the disk space. I also want the queue processed as fast and as often possible. Thanks, Brian Seppanen seppy@chartermi.net 906-228-4226 ext 23 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html