Holger Parplies schrieb:
> > 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.
> [downgrade debian tar]
>
> 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'.
Luckily the deb was still in my apt cache. I set the packet on hold
now. I thought about this before, but I would like a solution that is
working wth the new tar too. I think it's just a question of time
until Craig will come up with a better solution.
> 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").
I've just updated/installed 3 debian etch servers - more to come ;)
> 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 ;-)
Downgrading to tar <1.16 seem to me to be the preffered method at the moment.
> - 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.
Yes.
> I hope someone can give you a better solution.
I think it's funny that this change was not classified as "Incompatible change"
in the Changelog...
Ralf
-------------------------------------------------------------------------
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/
