Davide,
Thanks for your reply. I can see your points. It was just a question I
had as it seems alot of the daemons I use, use the apache style or a single
config file method. The daemons also don't lock the files when reading them,
they just read them upon startup (of course) and re-read them automatically
within a certain period of time (to check for any changes made to them). I
suppose both styles have their strengths and weaknesses. In either case,
thanks for the reply.
Dave
Davide Libenzi <[email protected]> wrote: On Mon, 19 Feb 2007, Dave
Henderson wrote:
> Gang,
> I have not used xmail very much (or any email daemon for that matter) but
> had a question regarding the configuration files for xmail. I noticed that
> it uses several many different files and wondered if there was ever going to
> be any type of consolidation into, say, an Apache style config file. What
> are the pro's and con's to that approach? Is this an idea that any one else
> shares?
Files in a folder are easier to spot than sections inside a huge
configuration blob. Updating a specific 4 lines config file, does not
require a lock over the whole config file. No, that's really not a good
idea. And it'd have had to be a *really* good one, in order to change all
over the code and break compatibility with the install base.
- Davide
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
