Sandra Panesso wrote: > > ? gtar: > >./etc/amanda/miro_daily/index/ernst.tomandandy.com/_Local_Library_CVSRoot/20010111_1.gz.tmp: > Warning: Cannot stat: No such file or directory Clear: No such file or directory! But why? Well, have a look at the name: 0010111_1.gz.tmp. This means that it is a temporary file. Probably this tmp file was there when tar started, but was not there when tar came to archiving it. No problem, rather normal. > ? gtar: ./mailman/logs/qrunner: file changed as we read it Clear again: file changed as we read it! But why? Have a look at the name again: ./mailman/logs/qrunner. This is a log file for some mail program. Is it that strange that it changed while tar was running? I don't think so. So, don't panic ;-) But why then AMANDA calls these info lines "STRANGE"? Because she does not understand them and thinks it is better to mark them "STRANGE" and forward them to you. If you want to eliminate them, you have to ensure that no file changes during AMANDA's run. Here's how AMANDA works in this respect (stolen from the list): Amanda watches the stderr lines from the backup program and pattern matches them against things it expects (normal). Every other line is considered "strange". If the backup failed or there were any strange lines, it reports them in this section of the E-mail. The character at the front of the line is a code for the class of line: | a normal (expected) line ? a strange (unclassified) line --- Regards Chris Karakas Don´t waste your cpu time - crack rc5: http://www.distributed.net
