Claudio Martins wrote:
Hi again,
I dug a little in Amanda code and found the reason why it was still
complaining about Strange dumps, even though the behavior with respect to tar
exit codes had been fixed.
Please consider including the patch below on the next Debian Amanda packages
release.
Thanks. Best regards
Claudio Martins
--- orig/amanda-2.5.1p3/client-src/sendbackup-gnutar.c 2006-11-24
18:10:38.000000000 +0000
+++ new/amanda-2.5.1p3/client-src/sendbackup-gnutar.c 2007-04-25
00:01:44.000000000 +0100
@@ -51,7 +51,9 @@
/* GNU tar 1.13.17 will print this warning when (not) backing up a
Unix named socket. */
AM_NORMAL_RE(": socket ignored$"),
-
+ /* GNU tar 1.16.1 will print this warning when a file changes while being
+ read. This is not fatal. */
+ AM_NORMAL_RE(": file changed as we read it$"),
/* GNUTAR produces a few error messages when files are modified or
removed while it is running. They may cause data to be lost, but
then they may not. We shouldn't consider them NORMAL until
I don't think this is a good idea. The file changing _is_ a problem. I
definitely prefer that amanda not abort the entire backup because of it,
but it's definitely a sign that the backed up file might not be a valid
backup. It's probably only valid if the file is an append only file,
such as a log.
Later,
Brad
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
