Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: cygwin bughunt (snapshot) Date: Mon, 28 Feb 2005 18:16:24 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <79F81D5F4790D344B05F489CE2AC8AB7146D63@dubexdc03.dubex.net> Message-ID: X-OriginalArrivalTime: 28 Feb 2005 18:16:24.0203 (UTC) FILETIME=[9C88C5B0:01C51DC1] ----Original Message---- >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 > /var/ready-quick/ > /var/ready-quick/file1 > /var/ready-quick/file2 > /var/ready-quick/file3 > /var/ready-quick/file4 > /var/ready-quick/file5 > +++ 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. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/