On Tue, May 25, 2010 at 01:28:19PM -0500, Les Mikesell wrote: > On 5/25/2010 1:13 PM, Robin Lee Powell wrote: > > > >> > >> That's a fantastic idea! I don't even need to do anything > >> complicated; just use "lockfile /tmp/backuppc" OSLT, since I > >> only care about not overloading single hosts. > > > > There is a problem with it, though: it can lead to starvation. > > I've got one host broken up into 10 or so backuppc jobs, and one > > of them has yet to run, 10 days later. Each of the jobs takes > > about 6 hours, which means it takes more than a day for them all > > to complete, which means 5+ jobs are always available to run, > > and that one just hasn't gotten lucky yet. > > > > Haven't come up with a good solution yet. > > I always thought the scheduling was ordered by the time since the > last backup or time since the backup was due - but I've never > gotten far enough behind to tell. Don't the backups that haven't > completed the previous day start first?
I don't know, but regardless there are always at least 5 of those, is what I'm saying. -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@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
