This is the mail archive of the
mailing list for the Cygwin project.
RE: cygwin bughunt (snapshot)
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Mon, 28 Feb 2005 18:16:24 -0000
- Subject: RE: cygwin bughunt (snapshot)
>From: David Dindorp
>Sent: 28 February 2005 17:54
> Evidence: See the order of execution in the script below,
> compare with what bash does (further below).
> Log file:
> +++ tar --remove-files --ignore-failed-read -cvf \
> /0007-02-2005-02-28-14-05-06-readyarchive_quick.tar ready-quick
Hmm. You appear to have told tar to create the output archive in the root
directory of the filing system.
> +++ cerr=0
> +++ sleep 30
> +++ '[' 0 -ne 0 ']'
> +++ '[' -f 0007-02-2005-02-28-14-05-06-readyarchive_quick.tar ']'
Hmm. You appear to be testing for the existence of said archive in the
current working directory, which I strongly suspect is /var. I would
_expect_ the -f test to fail in this case, although I'm at a loss as to why
$arcrfname would have had a slash at the beginning when you passed it to the
tar command but has now somehow lost that slash....
> ++++ date '+%Y-%m-%d %H:%M:%S'
> tar: Removing leading `/' from member names
> +++ echo '2005-02-28 14:05:07: TAR failed.'
Hmm. The fact that the stderr output is buffered somewhere along the line
and only now emerges may be entirely a red herring.
Can't think of a witty .sigline today....
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html