Re: Locking and concurrency -- system considerations

Top Page
Delete this message
Reply to this message
Author: Nigel Metheringham
Date:  
To: Jon Morby
CC: Philip Hazel, exim-users
Subject: Re: Locking and concurrency -- system considerations
There is, of course, a way of avoiding all of this pain.

In the config file use
    spool_directory = /var/spool/exim/${primary_hostname}


or something similar, make sure the logs are in a similar location, and
run each machine in its own spool directory.

If a machine dies, then you start another exim queue runner with a
fractionally modified config file (maybe the possibility of setting these
variables on the command line should be looked at??).

Then you don't *really* have shared directories, your locking problems
disappear in a puff of logic, and you have a decent solid spool area.
You are still canned if your NFS server dies, but then so are we (for
different reasons).

    Nigel.


-- 
[ Nigel.Metheringham@???   -  Systems Software Engineer ]
[ Tel : +44 113 251 6012                   Fax : +44 113 224 0003 ]
[            Friends don't let friends use sendmail!              ]




--
* This is sent by the exim-users mailing list.  To unsubscribe send a
    mail with subject "unsubscribe" to exim-users-request@???
* Exim information can be found at http://www.exim.org/