On Sun, 13 Mar 2011 16:34:07 +0000, Sam Tygier <Sam.Tygier@hep.manchester.ac.uk> wrote:

> sounds like just the problem Dustin Kirkland was trying to solve with
> run-one and run-this-one 
> 
> http://blog.dustinkirkland.com/2011/02/introducing-run-one-and-run-this-one.html
> 
> the comments also mention a command flock, that might do the same job

Thanks for the pointers. So far I think the suggestion of running them
on different days is winning for this particular situation.

All the best,

David

On Sun, 13 Mar 2011 16:20:16 -0700 (PDT), Jim C <jimcooncat@yahoo.com> wrote:

> Locking can cause problems of its own at times. I think a simpler way
> would be to run your basic job Saturday - Thursday and your
> comprehensive job on Friday (or some such schedule). Should come out
> so its easy for your replacement to figure out by looking at the
> crontab.

That's a good suggestion as far as I can see. The incremental backup
isn't going to be that useful on the day the full backup runs anyway.

Thanks,

David