-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gert Brinkmann wrote: > as I am setting up dirvish I find that it is some work to define > all vaults and include/exclude rules. What is the best solution > to back this dirvish.conf's up to have them in a history?
These days, I do my revision controlling for such things with subversion. Just make the dirvish/ directory inside each vault a working copy of <your-dirvishconfig-repository>/<vaultname> and setprop the ignorelist to include default.hist. The same way, you can have the /etc/dirvish/ directory for each host in <your-dirvishconfig-repository>/master-<hostname>. I'd guess any other system right down to rcs would work well (in fact, the locking by default might be preferable for many system administration task). Note that svn does not only not preserve permissions but rather resets them to your umask aggressively on simple updates. Most version control systems do that as far as I know, they're for writing software, not config files. > Wouldn't it be better to store them in /etc/dirvish/ instead in > the vaults? You could do that and softlink the files to /etc. I'd imagine it's because it makes moving vaults between hosts and filesystems easier, so I'd leave it in the vaults. Best of luck, Bernd PS: Please make your lines a little shorter. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPPo0jAQAqv3HuJURApOoAJ9h8KJoZVHw9tIs3zDhDPYfHhaUZwCdEx9W ASRL3VAPpYWrwoPD5H59Tc8= =WKjy -----END PGP SIGNATURE----- _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
