|
Re: [BackupPC-users] Parity (par2) command running on archives even though set to 0
2012-03-20 11:03:11
On Tue, Mar 20, 2012 at 9:30 AM, Timothy J Massey <tmassey AT obscorp DOT com>
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 command is clearly being
> logged by BackupPC. I'm really surprised that the log output isn't enough to
> cause BackupPC to reset its timer.
>
> My Perl-fu is relatively weak, but I'll try to take a stab at it... If
> anyone has any suggestions on where to look, I'm all ears! :)
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...
--
Les Mikesell
lesmikesell AT gmail DOT com
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
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/
|
|
|
