It's a new features of tar-1.16
Try the attached patch.
Jean-Louis
Tony Lill wrote:
I'm running amanda 2.5.1p1 on sparc/solaris with gnu tar v1.16, and tar
is exiting with error code 1, presumably because some files have changed
while they were being read.
I thought that amanda was supposed to ignore such errors. At least I've
never had a backup fail for this reason on earlier versions of
amanda/tar.
I checked out sendbackup, and I don't see any code ignoring exit 1 from
tar. I thought that tar always exited with 1 if a file changes and 2 for
other errors or am I just going mental? Is this something new with tar
1.16? The info file with that version specifically mentions exit 1, but
on earlier version, the doc is a bit vague.
--
Tony Lill, [EMAIL PROTECTED]
President, A. J. Lill Consultants fax/data (519) 650 3571
539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461
--------------- http://www.ajlc.waterloo.on.ca/ ----------------
"Welcome to All Things UNIX, where if it's not UNIX, it's CRAP!"
diff -u -r --show-c-function --exclude-from=amanda.diff amanda-2.5.2alpha.new/client-src/sendbackup.c amanda-2.5.2alpha.new.tar/client-src/sendbackup.c
--- amanda-2.5.2alpha.new/client-src/sendbackup.c 2006-10-20 07:55:19.000000000 -0400
+++ amanda-2.5.2alpha.new.tar/client-src/sendbackup.c 2006-11-15 11:25:29.000000000 -0500
@@ -605,6 +605,11 @@ check_status(
}
#endif
+ if(pid == tarpid) {
+ if(ret == 1) {
+ rc = 0;
+ }
+ }
#ifdef IGNORE_TAR_ERRORS
if(pid == tarpid) {
/*
