From: Les M. <les...@gm...> - 2012-03-19 22:34:29
|
On Fri, Mar 16, 2012 at 12:30 PM, Timothy J Massey <tm...@ob...> wrote: > > While we're on the subject: what could I do to get BackupPC to realize that par2 is doing its thing even if it doesn't think it's seeing output from the command? It's certainly spewing plenty of things out while it's working: it outputs something for every 0.1% of output it processes... Then I would be able to generate parity for things that take more than 1200 minutes if I wanted to. (Yes, I know I can change the limit. I'd like to: to much *shorter*, by making BackupPC aware that the parity process is still working!) It's a longstanding bug that some things that should advance the timeout don't. I'm not sure if anyone has ever tried to track it down or if it is just elusive. -- Les Mikesell les...@gm... |