I'm sure this question as been asked before but googling has not turned up much useful information about what causes it and how to ignore or prevent it.
I'm running gnu tar version 1.20 on Solaris 10. I am tarring about 20 file each about 2g in size. If I run this process during the day it completes with a 0 exit code. If I run it exists with a non-zero exit code and reports "file changed as we read it". Inspecting whats in the archive reveals that none of the files' contents changed. My question is why am I getting this error and how do I ignore it. I do know that the o/s backups (using net backup) are hitting the same directory at night while the tar command is still running and I *suspect* that the warning is related to this, but now knowing what tar thinks is changing, I can't prove it. TIA
