On 15 Jul 1998, Harald Meland wrote:
= [Sherwood Botsford]
=
= > The following steps solve the problem.
= >
= > 1. chown mail /opt/exim/bin/exim
= > 2. chmod u+s /opt/exim/bin/exim
= > (On this system chown clears the setuid flag)
= >
= > 3. rm -rf /var/spool/exim
= > 4. mkdir /var/spool/exim
= > 5. chown mail /var/spool/exim
= >
= > Is this likely to get me into other trouble?
=
= Exim won't be able to bind to port 25 when running with a non-zero
= uid. If you're running exim from inetd, and let inetd (running as
= root) do the binding for you, this won't be a problem. Otherwise, it
= most likely will get you into trouble...
=
Hadn't thought of that, but since the daemon is started by one of the
startup scripts that runs as root, it seems to work.
BUT it initally didn't work because the log file was owned by mail,
group root, and the starting daemon didn't have write permission.
Chowning the spool tree to be group root, and making it group writable
solved that one.
Sherwood Botsford | email avatar@???
Sorcerers Apprentice | Office CAB 642B
System Administrator | Tel: 403 492 5728
Trouble shooter | Fax: 403 492 6826
--
*** Exim information can be found at
http://www.exim.org/ ***
