On Tue 19 Sep 2006, Keith Lofstrom wrote: > I can't speak for hanj, but it is reasonable to run all the expires > at once. However, hanj is not including the vault FOO in master.conf, > only in master2.conf, so dirvish-expire will not automatically run > vault FOO either. That actually allows more freedom for hanj, because
Not quite true... dirvish-expire will search the entire bank(s) that is specified in the master.conf for any images that are expired; dirvish-expire doesn't care about vaults. I've noticed that with vaults for systems that have become obsolete: the vault definitions are removed from master.conf, but (after some time) dirvish-expire complains about "cannot expire vaultname:default:YYYYMMDD No unexpired good images" which is pretty good actually :) It's even wierder sometimes, depending on how you look at it: we had renamed a system and had renamed the vault accordingly (and fixed master.conf and the default.conf inside the vault). dirvish-expire gave the above error message with the old host name; it gets its info from the summary file, the location of the image within the bank is irrelevant. Of course, it could be that hanj has a separate bank defined in master2.conf (I seem to have deleted his message already), in which case he needs to manage it separately. Paul Slootman _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
