Perhaps so. When I saw the term "exit status" I immediately read the
tar(1) man page and found that the exit status for that command is 0, 1
or 2. As I say, it misled me.
Paul
On 29/11/2020 13:42, backu...@kosowsky.org wrote:
> Not misleading. It's a perl standard and backuppc is written in per
Not misleading. It's a perl standard and backuppc is written in perl.
Paul Leyland wrote at about 08:22:05 + on Sunday, November 29, 2020:
> Thank you. I would argue that reporting an exit status of 512 when
> tar(1) returns 2 is misleading. It misled me anyway.
>
> The source of the pr
Thank you. I would argue that reporting an exit status of 512 when
tar(1) returns 2 is misleading. It misled me anyway.
The source of the problem is that localhost.pl ran a tar(1) locally
under the backuppc account and did not set the --ignore-failed-read
option. Using the generic $Conf{TarClien
The reported exit status is shifted left by 8 bits, so that means tar
exited with status 2, which means failure.
You should look at the XferLOG to see what error(s) it reported. It could
be something benign, but you should be sure before you start disabling
error checking.
Craig
On Sat, Nov 28,
This is a golden oldie. At least a decade after
https://sourceforge.net/p/backuppc/mailman/backuppc-users/thread/AANLkTi%3DuzdiYV1jCzofkfeEQ6-czx34uEmYx2159Uxa%2B%40mail.gmail.com/#msg26616969
appeared, Ubuntu still ships with a backuppc which reports
backup failed (Tar exited with error 512 () s
