Timothy J Massey wrote at about 12:05:02 -0400 on Thursday, May 31, 2012:
> Pascal Mosimann wrote on 05/31/2012
> 11:12:54 AM:
>
> > > Why does BackupPC run the parity command if I've told it not to by
> > passing
> > > it a 0? And how do I return to the 3.1 behavior? According to the
Pascal Mosimann wrote on 05/31/2012
11:12:54 AM:
> > Why does BackupPC run the parity command if I've told it not to by
> passing
> > it a 0? And how do I return to the 3.1 behavior? According to the
> > documentation, setting it to 0 should disable it, not cause it to run
> with
> > a
> Why does BackupPC run the parity command if I've told it not to by
passing
> it a 0? And how do I return to the 3.1 behavior? According to the
> documentation, setting it to 0 should disable it, not cause it to run
with
> a parameter of 0... And if for some reason we would *want* the
pa
Les Mikesell wrote on 03/20/2012 11:01:56 AM:
> The places where it works, it should be doing a
> alarm($conf->{ClientTimeout})
> to set/advance the timer. But you need to find the places where it
> doesn't do this...
Well, here's the relevant code from BackupPC_archiveHost that runs the tar
On Tue, Mar 20, 2012 at 9:30 AM, Timothy J Massey wrote:
>
> >
> > 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.
>
> Yeah. What's weird is that the output of the par2 comman
Les Mikesell wrote on 03/19/2012 06:34:22 PM:
> On Fri, Mar 16, 2012 at 12:30 PM, Timothy J Massey
> 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 cert
On Fri, Mar 16, 2012 at 12:30 PM, Timothy J Massey 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: i
Hello!
I have set up a couple of BackupPC 3.2.1 hosts (using the EPEL package).
For some of my archives, the size is too large for par2 to complete in
1200 minutes (the default limit for archvies without response) and for
some reason, BackupPC does not see the fact that par2 is doing something,
