Hi, Tar should complain and die if an input path doesn’t exist. So, no, the behaviour you’re seeing isn’t broken. See also:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205358 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205358> This bug has been fixed upstream seems to have been imported into stable/10 in r302075. From the commit message: - tar and cpio should fail if an input file named on the command line is missing (vendor issue 708) I agree the message could be a bit clearer about what’s going on! Regards, Jan. > On 6 Jul 2016, at 02:39, Tim Daneliuk <[email protected]> wrote: > > I just upgraded to r302342 today to verify a problem I saw > after a 10.3-STABLE upgrade yesterday. Upgrade was > accomplished via makeworld/kernel & installworld/kernel. > > > When using tar with the -T argument to provide a list > of backup sources, it blows out with the following > error if a source in the file list is missing: > > tar: INTERNAL ERROR: Function 'archive_read_disk_open' invoked with archive > structure in state 'header', should be in state 'new/closed': Unknown error: > -1 > > In the past, tar would make some noise if it was asked > to copy a nonexistent file or directory, but it would > continue the remainder of the archive operation. > > Thoughts? > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[email protected]" _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
