[Exim] logging of non writable log files

Top Page
Delete this message
Reply to this message
Author: Lutz Pressler
Date:  
To: exim-users
Subject: [Exim] logging of non writable log files
Hello,

recently I had to debug an Exim (4.20) installation, where compiled
in exim_user ("mail") and that set in the configuration file(s)
("exim") had been different (in name and uid) - and different
daemons were started with -C to have multiple configurations.

This leads to the situation, that the (remote) deliveries do not
turn up in the log file at all, probably because the log file is
owned (and writable) by "exim", the delivering processes running
as "mail" though.

No trace in paniclog (same situation) and syslog either.
Maybe that could be improved, as the spec in chapter 44 states
"When Exim cannot open its panic log, it tries as a last resort
to write to the system log (syslog). This is opened with
LOG_PID+LOG_CONS and the facility code of LOG_MAIL. The message
itself is written at priority LOG_CRIT."

Greetings,
Lutz

--
  _              |  Lutz Pressler          |  Tel: ++49-551-3700002
 |_     |\ |     |  Service Network GmbH   |  FAX: ++49-551-3700009
 ._|ER  | \|ET   |  Bahnhofsallee 1b       |   mailto:lp@SerNet.DE
Service Network  |  D-37081 Goettingen     |  http://www.SerNet.DE/