Re: exit status patch

[Colin Percival <cperciva@tarsnap.com>]

Hi all,

On 10/10/10 23:54, jon stuart wrote:
> One of the filesystems that I run tarsnap across contains directories
> that are reasonably volatile: files and subdirectories may be deleted by
> a content management process during tarsnap's run.
> 
> Defiencies in this situation aside, I need to be able to distinguish
> between tarsnap's surprise when files disappear between its feet and
> other less expected errors, such as a network failure or similar. [...]

Hmm, good point.  A couple of years ago I adjusted the handling of "file
has grown while being archived" to make it a non-error; it seems reasonable
to me that "file disappeared before we managed to archive it" should be
handled the same way.

I'd like to keep Tarsnap consistent with bsdtar here, though, and I'm not
quite sure why bsdtar treats these as errors -- Tim, can you comment on
this?

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid