I don't like the idea of recreating files based on processed maps in memory. Although it would be reasonable for passwd and hosts, it would be a pain for auto.master and auto.* and whatnot. Not to mention the loss of comments and formatting.
I think this is what I'll do -- Each time I update the files and will do a make, I'll check the files into svn. And that oughta do 'er. Thanks for the suggestions everyone. -----Original Message----- From: Steven M Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 2:57 AM To: Eddy Harvey Cc: [email protected] Subject: Re: [BBLISA] Help setting up NIS (or alternative to NIS.) I'm pretty sure we used to promote slaves to masters in this sort of situation. And that it was possible to regenerate the source form of the maps from the preprocessed versions the slaves keep. Of course you do lose comments and formatting... Similar to what other folks are saying, I'd be tempted to set up a periodic rsync-over-ssh job to keep a copy of the source maps on the slave. Seems like the easiest way to deal with it. And hey, you're already expending resources to make sure the secondary is up and available, so why involve a third host? Just wish all the systems I'd check this out on weren't in storage... Good luck, let us know how you decide to deal with it. --Steve. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.3/107 - Release Date: 9/20/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.3/107 - Release Date: 9/20/2005 _______________________________________________ bblisa mailing list [email protected] http://www.bblisa.org/mailman/listinfo/bblisa
