Hi !!
> You do realize, I hope, that this means Exim will have to open and read
> n files instead of 1 each time a new Exim delivery process is started,
> which can be very often on a busy system. It maybe that in your
> enviroment this is not noticeable, but...
what about using something like mmap to memory map the config file to avoid
reading it every time a new process is started ?
> [Aside 1: Smail used multiple config files; for Exim I went for one file
> instead, partly for the performance reason, but partly because I want to
> be able to see the whole thing at once in my editor. Seems like not
> everyone feels this way. :-]
it's very useful if you have parts of the configuration that are shared
across many servers (main settings, acl settings, ...) so you only need
to change one file and propagate it to the other servers (as opossed to
manually edit one config file in each server or having to use diff/patch)
It makes also possible to distribute small config parts (like complex
acl) that could be easely integrated into existing configurations.
--
Bestv regards ...
Take my advice, I don't use it anyway.
----------------------------------------------------------------
David Saez Padros http://www.ols.es
On-Line Services 2000 S.L. e-mail david@???
Pintor Vayreda 1 telf +34 902 50 29 75
08184 Palau-Solita i Plegamans movil +34 670 35 27 53
----------------------------------------------------------------
