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. Thanks, Brian Seppanen seppy@chartermi.net 906-228-4226 ext 23
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. -- Nate Campi http://www.campin.net
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
On Tue, Feb 04, 2003 at 02:31:51PM -0500, Brian E. Seppanen wrote:
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.
See if you can have the daemon log to local7.notice or something that you don't capture with syslog-ng. This way you don't even have to log it to /dev/null. -- Nate Campi http://www.campin.net
On Tue, Feb 04, 2003 at 01:53:29PM -0800, Nate Campi wrote:
On Tue, Feb 04, 2003 at 02:31:51PM -0500, Brian E. Seppanen wrote:
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.
See if you can have the daemon log to local7.notice or something that you don't capture with syslog-ng. This way you don't even have to log it to /dev/null.
perm(-1) should do the trick. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (3)
-
Balazs Scheidler
-
Brian E. Seppanen
-
Nate Campi