Well, it is obvious that your Big Brother log file is being written to while your backup occurs, which can happen. What version of gnutar are you using? I get these messages a fair amount, but they generally only result in a warning from gnutar, not a fatal error.
-- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge [EMAIL PROTECTED] On Tue, 20 Nov 2001, Murari wrote: > Hi > I would like to know why amdump says FAILED in different days. I've given > the complete details for both days below. Please let me know what I have to do. > Thanx, Murari > > FAILURE AND STRANGE DUMP SUMMARY: > plum /grove1 lev 0 FAILED [/usr/freeware/bin/tar returned 2] > FAILED AND STRANGE DUMP DETAILS: > /-- plum /grove1 lev 0 FAILED [/usr/freeware/bin/tar returned 2] > sendbackup: start [plum:/grove1 level 0] > sendbackup: info BACKUP=/usr/freeware/bin/tar > sendbackup: info RECOVER_CMD=/usr/freeware/bin/tar -f... - > sendbackup: info end > ? gtar: ./people/bigbro/bb18b3/BBOUT: file changed as we read it > | Total bytes written: 3864524800 > ? gtar: Error exit delayed from previous errors > sendbackup: error [/usr/freeware/bin/tar returned 2]
