Hi, Ralf Gross wrote on 19.01.2007 at 09:32:01 [Re: [BackupPC-users] tar error 256]: > Craig Barratt schrieb: > > What version of tar are you using? Torsten reported that the > > newest version has changed the exit status in the case of > > certain relatively benign warnings that are therefore considerd > > fatal by BackupPC. > [...] > > Is there a workaround for backuppc 2.x or 3.x? I'm seeing more of these errors > and it's definitively because of a file that has changed during read.
supposing you don't really need tar 1.16 on the client machine(s), you could always downgrade to tar 1.14 from sarge (or a previous 1.15 from etch) until there is an official solution. Note that the current sarge tar package is a security update. From DSA-1223-1: > i386 architecture (Intel ia32) > > http://security.debian.org/pool/updates/main/t/tar/tar_1.14-2.3_i386.deb > Size/MD5 checksum: 499560 c764b0894f6c3317a78124177cfed9fe > > ia64 architecture (Intel ia64) > > http://security.debian.org/pool/updates/main/t/tar/tar_1.14-2.3_ia64.deb > Size/MD5 checksum: 543432 0dc8b4d66a82d05d7b68f2dbee960791 > > amd64 architecture (AMD x86_64 (AMD64)) > > http://security.debian.org/pool/updates/main/t/tar/tar_1.14-2.3_amd64.deb > Size/MD5 checksum: 503902 98a8169210eb273252a7997c726c4333 > > sparc architecture (Sun SPARC/UltraSPARC) > > http://security.debian.org/pool/updates/main/t/tar/tar_1.14-2.3_sparc.deb > Size/MD5 checksum: 499698 d260b9f5db00b12414d6136c63e37202 You can either download the relevant file (and preferably verify its checksum against the one listed on the Debian web site, which should hopefully correspond to the one I quoted :) and 'sudo dpkg -i' it (perhaps first test with 'dpkg --no-act -i ...'), or preferably add deb http://security.debian.org/ sarge/updates main to your sources.list and % sudo apt-get update; sudo apt-get install tar=1.14-2.3 to install it. This has the advantage of warning you first, should something installed on your system depend on a newer version of tar (in a more readable format than the 'dpkg --no-act ...'). Once downgraded, prevent upgrading to the etch version again with % echo 'tar hold' | sudo dpkg --set-selections (which you would later undo with % echo 'tar install' | sudo dpkg --set-selections when you want to switch to the etch version again). All instances of 'sudo' are meant to document what requires root priviledges and what doesn't. You can, of course, do everything as root without 'sudo'. I don't really like that approach, and it might be cumbersome if you are talking about many client machines, but otherwise it's rather easy to do and probably safe (and you wrote "one machine"). Another possibility could be to write a wrapper around either ssh on the server or tar on the client to change an exit code of 1 to an exit code of 0, but that probably has the problem of affecting more serious errors as well (if it was as simple as patching exit code 1 to 0, I guess there would be a fix in place already). You could even do this in BackupPC itself, *possibly* as simple as changing line 213 (in 3.0.0beta3) in Xfer::Tar.pm as in - if ( !close($t->{pipeTar}) ) { + if ( !close($t->{pipeTar}) and $? != 256 ) { but that a) is *totally* untested, b) will affect all clients and not only one and c) will make all failures returning exit code 1 to be regarded as "ok" (provided it even works) d) will of course void your BackupPC warranty ;-) - four good reasons not to try it unless you are really desperate :-). With a wrapper around ssh or tar you can at least limit the effect to one client. But downgrading tar still seems safest to me. I hope someone can give you a better solution. Regards, Holger ------------------------------------------------------------------------- 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/
