Quoting Christoph Scheeder <[EMAIL PROTECTED]>: > Hi, > the first strange message is produced because you told amanda to > backup it's own index-files, and they are changing while the backup > is running. > So tar complains about a file it saw while looking for files to backup, > but whene it tried to backup that file it had been removed by amanda.... > > it's no good idea to backup the active index-directory. > > and the second means the mentioned file was changed by another process > while tar was reading it for the backup. > Is it a log-file of another process? > if yes i would although exclude it from backup. Is there a way to tell amanda what errors from tar to ignore? Some sort of regexp we could program somewhere? We get a ton of the "file changed" messages and the "file is a socket, backing up anyway" messages, and they are quite the pain. We don't care that a file is a socket, nor that the file changed as we read the thing. If we could get amanda to realize those messages aren't to be interpreted as problems, at least with certain files on certain hosts, that would help us immensely. rob ------------------------------------------------- This mail sent through IMP: http://webapps.myinternetplace.net
