Holger writes:
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,
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.
Could you also look through the XferLOG file and confirm that
it
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
- Craig Barratt [EMAIL PROTECTED] wrote:
[snip...]
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.
Both client and server are
Running into a problem with my larger machines doing backups. 90% of the time,
the backup ends with the following message:
backup failed (Tar exited with error 256 () status)
I believe I read somewhere that it was due to a file changing during backup,
probably in combination with the latency
Bradley writes:
Running into a problem with my larger machines doing backups. 90% of
the time, the backup ends with the following message:
backup failed (Tar exited with error 256 () status)
I believe I read somewhere that it was due to a file changing during
backup, probably in
Craig Barratt schrieb:
Bradley writes:
Running into a problem with my larger machines doing backups. 90% of
the time, the backup ends with the following message:
backup failed (Tar exited with error 256 () status)
I believe I read somewhere that it was due to a file changing during
