This can still be maintained in the old system if you allow includes
just like apache, where you can have the main file include other files.
Then you would have your own hierarchy of configs that could infact
resemble this one and still allow others to use a single simple to edit
monolithic file.
-----Original Message-----
From: vserver-bounces@list.linux-vserver.org
[mailto:vserver-bounces@list.linux-vserver.org] On Behalf Of Oliver
Welter
Sent: Sunday, April 23, 2006 11:44 AM
To: vserver@list.linux-vserver.org
Subject: Re: [Vserver] great flower page
Hi Folks,
> I'm agree, I've prefered the old vserver style to configure with one
> file per vserver like in freevps
> Moreover most of Linux program use only one file to config ...
> I don't see where is easier to maintain it ? ...
It's much easier to deploy and modfiy the configuration on this basis
when using automated scripts...I use vserver to implement some failover
stuff and unfortunately the boxes differ sligthly - this way its much
easier to sync only certain files, and ignore others. Besides it is
easier to just put some own config stuff vor own scripts.
So I prefer this style as it is easier to manage by scripts
Oliver
-- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72 _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Sun Apr 23 16:24:41 2006