Hello Oumar, thanks for your reply, Ok, I understand. I thought you were tarring individual files bc. the changed file name was displayed in the error message. In my tests with tarring modified files the error message would only give me the folder name that I was tarring. So I think this is a special message when using --listed-incremental.
To be fair I am not really sure if tar really quit service when it read the modified file. I thought so because the error message was at the end of the log but this may just be some summary message after the process finished its complete file list like expected. Maybe it is just the exit code 1 which lets nssbackup think that the backup failed? I see from the source code that everything != 0 currently is regarded a failed backup. Maybe accepting 1 with some warning message may do the job? "Unfortunately" I currently have no failed backups to further analyze the tar behaviour in nssbackup. I will look if I can reproduce the problem and then see if the tar archive is intact. -- Option to ignore "file changed as we read it" https://bugs.launchpad.net/bugs/400145 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. _______________________________________________ Mailing list: https://launchpad.net/~nssbackup-team Post to : [email protected] Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
