I'm using rsync to cygwin-rsyncd (from BackupPC website). It seems as though the filelist is coming back just fine, as this particular backup always makes it part way through, until it runs into a 4GB file. I can see BackupPC creating partial files (I'm not sure why). It creates something like:
And then I get the alarm caught error.
(Very briefly) Looking through the code for BackupPC_dump, I only see one call to alarm() and only one reference to ClientTimeout in the entire bin directory.. I'm not sure how you're handling resetting the alarm as data flows in, but I don't think it's working correctly in beta0 at least.
Thanks again for all your help.
Director of IT Operations
115 Broadway, 2nd Fl.
New York, NY 10006
08/23/2003 08:05 PM
Subject: Re: [BackupPC-users] ClientTimeout
> According to the documentation, ClientTimeout should be how long
> BackupPC_dump waits for output from the client program before aborting the
> dump. It appears that the default is 2 hours. I have a couple of backups
> that are actually not finishing in the two hour time limit, so I simply
> changed it to 4 hours (not even sure if that's enough, I've got to grab
> about 40GB).
> At any rate, ClientTimeout implies to me that BackupPC_dump is watching
> the output of the client program and resetting the alarm period every time
> more data is received. I may have missed it, but I don't think that's how
> it's implemented in 2.0.1beta0. Am I missing something?
Yes, it should reset the ClientTimeout when it sees some activity. Not
every time mind you (for efficiency reasons). But the code is specific
to the XferMethod. What are you using?
There could be long times when there is no network traffic; eg: rsync
builds the entire file list before sending it. On my WinXP laptop
that takes 30 minutes.