[syslog-ng]perm() bug in 1.4.13?

[Nate Campi]

--8NvZYKFJsRX2Djef
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 27, 2001 at 10:04:07AM -0500, Michael D. (Mick) Bauer wrote:
> If I define a logfile with perms "-rw-r------" using the following in
> syslog.conf:
>=20
>      destination d_micklog { file("/var/log/micklog"=20
>                  owner(mick) group(wheel) perm(0640)); };
>=20
> a file is created that looks like this (ls -l output):
>=20
>      -rw-------  1 mick  wheel   57 Sep 27 10:03 /var/log/micklog
>=20
> Why aren't the "group" bits being set? At first I thought maybe I needed
> to "invert" the mode a l=E0 umode, but that isn't it. Ideas?

The permission settings from within C code are still subject to the
umask of the user/process creating the file. Do you set a umask in your
init scripts? Do you start syslog-ng as root with a restrictive umask
setting?
--=20
	Nate

--8NvZYKFJsRX2Djef
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7s2WdWpDEZMF673kRAtHLAJ934QM2HaLPOVp0BjTAAdW7UmS29wCfSFGl
pSGkycR26xeh7kLfV1zgX+A=
=90Sy
-----END PGP SIGNATURE-----

--8NvZYKFJsRX2Djef--