On Tue, 19 Sep 2006 15:40:15 +0100 Dave Howorth <[EMAIL PROTECTED]> wrote:
> hanj wrote: > > This fires off at 3AM, which is great, but now I need to have dirvish > > run around 4PM for one particular server backup. I thought it would > > be easy creating a new master.conf file (master2.conf) in > > /etc/dirvish, and adding that argument to dirvish-runall with > > --config option and cron'ing my particular run time, but I'm not sure > > how to handle the dirvish-expire. I'm not seeing any configuration > > options for new config/alternative in the man page for > > dirvish-expire. Maybe I'm just going about this totally wrong. Any > > ideas? > > Does it matter when dirvish-expire runs? Why isn't it sufficient for it > to do its job on all vaults at 3am? It doesn't matter when dirvish-expire runs, but wasn't sure how to let dirvish-expire know about that image, since (I believe) it picks it from the run-all list (which I can't have, since I don't want it to run this image at 3AM) I wanted to run this at this time, due to a problem with SSH on their end. For some reason multiple SSH sessions can 'sometimes' disrupt each other leading to dropped connection. They have another offsite backup process running throughout the night for other files, and I don't want to interfere with that at all, since that backup (which I'm not a part of) is mission critical. If I can run at 4PM, I'd get my backup files without potentially hosing their backup. Thanks for the response. hanji _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
