On Tue, May 25, 2010 at 02:08:49PM -0500, Les Mikesell wrote:
> On 5/25/2010 1:55 PM, Robin Lee Powell wrote:
> >
> >>> I don't know, but regardless there are always at least 5 of
> >>> those, is what I'm saying.
> >>
> >> But are they the same 5?  If you simply can't transfer the
> >> amount of data you have there's not much it can do but pick up
> >> where it left off when wakes up outside of a blackout again.
> >> As long as it isn't the same jobs being missed repeatedly, it
> >> is probably going to the to it as fast as you would if you
> >> adjust the schedule anyway.
> >
> > It should take about 4 days to do all the jobs.  There's one job
> > that is 10 days old.  Therefore I conclude that it's not doing
> > the right thing.  :)
> 
> OK, agreed, but did you mention having some sort of custom lock
> that limits concurrency?  If that looks like a failure the job
> probably goes to the bottom of the list - and at startup, you
> would probably always fail most of the oldest jobs that try to
> start.

Yep, there's a simple lockfile semaphore, so if there's a job
already running then whatever other jobs on that host it tries will
fail out.  At some point, though, there's no jobs running; at that
point, the oldest should be tried first, and should not fail.
That's what I'd expect, anyways.

-Robin

-- 
http://singinst.org/ :  Our last, best hope for a fantastic future.
Lojban (http://www.lojban.org/): The language in which "this parrot
is dead" is "ti poi spitaki cu morsi", but "this sentence is false"
is "na nei".   My personal page: http://www.digitalkingdom.org/rlp/

------------------------------------------------------------------------------

_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/