Bug#399930: Maybe related to bug #379843

[Andreas Metzler]

On 2007-02-13 juanhm at lebowsky.homelinux.org wrote:
> I had the same proble with "/var/log/exim4/mainlog" permissions for some
> days, and I read what it´s stated in bug reports #399930 and #400198.
[...]
> "/etc/cron.daily/sysklogd" restarting the syslogd daemon ever day and
> "/var/log/exim4/mainlog" appearing in "/etc/syslog.conf".

> You can verify if this could be your case looking at the output from the
> command "syslogd-listfiles -a" and checking if "/var/log/exim4/mainlog"
> appears. If it appears, then both syslogd and logrotate are managing your
> exim log file, and for syslogd, it recreates the file with permissions and
> ownership "640 root:adm" if it doesn´t exists.

> For my case, I have removed "/var/log/exim4/mainlog" from
> "/etc/syslog.conf" and everything seems OK.

> I don´t know if this is related to your problem but, anyway, I find a bit
> confusing both syslogd and logrotate managing the same log files. So, I
> would be very pleased with any fix to bug #379843.

Hello,
Well, afaik no official Debian package of sysklogd has ever shipped a
/etc/syslog.conf file that handled /var/log/exim4/mainlog (For the
simple reason that exim does not log through syslog by default.)

So I think either you or another admin of this machine has somehow
manually generated this slightly broken configuration and there is
nothing the exim4 or sysklog packages can do about it.
cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'