i am not worried about the distribution mechanism, which is what your reply seemed to focus on. i was more uncertain about whether its one file or two (or whatever else might work). i interpret your reply as in favour of a seperate file for the local config.
(this is not to say that your points aren't well taken, but this is a design issue and the actual delivery/installation issues are subsumed by a "Process" over which i have no control.) On Sep 1, 2011, at 10:06 AM, Zack Williams wrote: > Is there a reason you're not embracing existing configuration management > tools (CFEngine, Puppet, etc.). > > If that's overkill, I'd put all the config in network enabled VCS (git or > similar), which should work well with your text-based config files, place > copies of the repo on every station, then use a script to hard link the > config file to it's working location (this way, if someone changes that > config file directly in it's working dir, they're also changing the file in > the repo). I'd organize based on server name or DNS information. > > - Zack ------------------ Andrew Hume (best -> Telework) +1 623-551-2845 [email protected] (Work) +1 973-236-2014 AT&T Labs - Research; member of USENIX and LOPSA
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
