[xmail] Re: config files discussion
Jeffrey Laramie wrote: > On Tuesday 20 February 2007 12:32, Davide Libenzi wrote: > >> On Tue, 20 Feb 2007, Dave Henderson wrote: >> >>> 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. >>> >> I'm not an heavy Apache user (actually, I use thttpd ;) but IIRC Apache is >> going in the exact opposite direction (splitting configs). >> > > In recent openSUSE releases httpd.conf is nothing more than comments and > Include statements. All the actual configuration is divided up amongst the > Included config files and directories. Most of the user configuration is in > vhost containers that each have a vhostname.conf file in the vhosts.d > directory. It takes a little getting used to but the design is actually very > nice once you see how it works. > > Jeff > - > 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] > > That's what my apache (and UnrealIRCd) config looks like too. But this will definately make updates from the CONTROL interface much harder, probably impossible for Davide. I agree with Francis Clement that it would be easier if most of the current command-line options were in the SERVER.tab or some other config file. Ivo - 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]
[xmail] Re: config files discussion
On Tuesday 20 February 2007 12:32, Davide Libenzi wrote: > On Tue, 20 Feb 2007, Dave Henderson wrote: > > 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. > > I'm not an heavy Apache user (actually, I use thttpd ;) but IIRC Apache is > going in the exact opposite direction (splitting configs). In recent openSUSE releases httpd.conf is nothing more than comments and Include statements. All the actual configuration is divided up amongst the Included config files and directories. Most of the user configuration is in vhost containers that each have a vhostname.conf file in the vhosts.d directory. It takes a little getting used to but the design is actually very nice once you see how it works. Jeff - 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]
[xmail] Re: config files discussion
On Tue, 20 Feb 2007, Dave Henderson wrote: > 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. I'm not an heavy Apache user (actually, I use thttpd ;) but IIRC Apache is going in the exact opposite direction (splitting configs). - 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]
[xmail] Re: config files discussion
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 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]
[xmail] Re: config files discussion
>-Message d'origine- >De : [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] la part de Davide Libenzi >Envoy=E9 : mardi 20 f=E9vrier 2007 16:28 >=C0 : 'xmail@xmailserver.org' >Objet : [xmail] Re: config files discussion > > >On Mon, 19 Feb 2007, Dave Henderson wrote: > >> Gang, >> I have not used xmail very much (or any email daemon for=20 >that matter) but had a question regarding the configuration=20 >files for xmail. I noticed that it uses several many=20 >different files and wondered if there was ever going to be any=20 >type of consolidation into, say, an Apache style config file. =20 >What are the pro's and con's to that approach? Is this an=20 >idea that any one else shares? > >Files in a folder are easier to spot than sections inside a huge=20 >configuration blob. Updating a specific 4 lines config file, does not=20 >require a lock over the whole config file. No, that's really=20 >not a good=20 >idea. And it'd have had to be a *really* good one, in order to=20 >change all=20 >over the code and break compatibility with the install base. > > >- Davide > > I agree with Davide, with exception for the cmd line parameters, as = these are the only 'external' parameters not in xmailroot but in deamon start script or registry (win32), that could be centralized in server.tab = file, keeping them usable on the cmd line to overwrite the server.tab = equivalent. Davide never respond to this request :( - 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]
[xmail] Re: config files discussion
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]
