Les Mikesell wrote at about 13:50:54 -0500 on Tuesday, September 1, 2009:
 > Jeffrey J. Kosowsky wrote:
 > >  
 > > Well (re)nice=20, would completely stop BackupPC_dump per my man pages at
 > > least:
 > >    20 (the affected processes will run only when nothing else in the
 > >    system wants to) 
 > 
 > I'm not sure about the scheduler internals, but I'd read the 'nothing 
 > else wants to run' as relating only to processes that aren't blocked 
 > waiting for i/o completion.  Since the nighly job spends most of its 
 > time in i/o, it "doesn't want to run" and the dumps will still be given 
 > CPU timeslices - which they will use to issue i/o requests.
 > 

I don't disagree. But it would probably be worthwhile for the OP to
try this to see what if any improvement he notices, since the effort
to implement it would be trivial and more general solutions are not
necessarily forthcoming. In less time than it took to pen this
response, the OP can just manually renice running dumps to see what
happens.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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/