On 14 January 2007 00:34, Holger Parplies wrote:
> while I perfectly agree that backing up temporary files has no advantage,
> the quoted case was
Yes, indeed, I don't backup the temporary dirs and I exclude lots of temporary
(and generated) files.
> Cristian Tibirna wrote on 12.01.2007 at 10:13:39 [[BackupPC-users] avoidable
failure?]:
> > [...]
> > So, once in a while, I get errors like this:
> >
> > ---------
> > Xfer PIDs are now 9356,9357
> > [ skipped 6674 lines ]
> > finish: removing in-process file
> > ctibirna-work/MEF/CVS-HEAD/GIREF/src/commun/Adaptation/.makedep
> > [ skipped 39 lines ]
> > Done: 15 files, 106665 bytes
> > Got fatal error during xfer (aborted by signal=ALRM)
> > Backup aborted by user signal
> > -----------
>
> which is an example of a temporary file that is obviously *not* located in
> /tmp or /var/tmp and can't be made to be.
And it is only an example. More drastic cases are those of files that are
undistinguishable from important ones, but are, still, created temporarily
(e.g. .c or .cpp files) by test scripts and such, and can appear and
dissapear during backup's activity. Those, I can't exclude. This is why I was
asking if there would be some way (which I overlooked, or which isn't yet
programmed into BackupPC) to ignore such errors and gracefully finish backups
even if files got removed between list generation and actual copying.
> You can still exclude such files, as I understand it, by adding them to
> $Conf{RsyncArgs} (at the end of the list). Something like
>
> '--exclude=.makedep',
> '--exclude=*.o',
>
> should do the trick (modify to suit your needs). Note that adding
> '.makedep' et al. to $Conf{BackupFilesExclude} will *not* work (at least
> not in version 2.1.1), as the code anchors relative paths to the root of
> the 'share'.
It works with $Conf{BackupFilesExclude} too. We use it extensively (to ignore
mp3, avi and .o files, mostly ;-)
> That said, 'aborted by signal=ALRM' does *not* sound like a temporary file
> problem to me (though I don't know what a temporary file problem *would*
> sound like). Might you simply need to increase your $Conf{ClientTimeout}?
> It would make sense that your backups take longer with busy client machines
> than with idle ones, after all.
Interesting suggestion. I will try to investigate more in this direction. I
don't know exactly was should be done as a matter of test though, as the
errors aren't reproduceable, as I mentioned in the beginning.
Thanks a lot for the suggestions
--
Cristian Tibirna (418) 656-2131 / 4340
Laval University - Québec, CAN ... http://www.giref.ulaval.ca/~ctibirna
Research professional - GIREF ... [EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
