[syslog-ng]permissions being changed for certain devices

[Balazs Scheidler]

On Mon, Sep 29, 2003 at 03:30:14PM +0100, Clemson, Chris wrote:
> 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.

use perm(-1) for those files.

-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1