X-Spam-Check-By: sourceware.org Message-ID: <00e701c6a387$8ebb2660$1e8d11d8@moose> From: "Brian Liedtke" To: Subject: Problem with embedded spaces in path name for --info-script switch in tar Date: Sun, 9 Jul 2006 12:43:23 -0600 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-IsSubscribed: yes 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 Using tar-1.15.1-4. I am writing a script to create multi-volume archives using tar. However it appears that the --info-script switch doesn't handle imbedded spaces in the path name. In the sample script below, I have hard-encoded the path to verify that was the problem and not with building the variable with the path name. Script: #!/bin/bash export ARCHIVE_DIR=/cygdrive/d export ARCHIVE_NAME=full_`date +%y%m%d` tar -cv \ --ignore-failed-read \ --exclude=pagefile.sys \ --exclude=*.vsv \ -L4096 \ -M --info-script="/cygdrive/c/Documents and Settings/Liedtke/My Documents/Tasks/Backup/rename.sh" \ -f$ARCHIVE_DIR/$ARCHIVE_NAME.tar . # End script Output is: tar: and: Warning: Cannot stat: No such file or directory. tar: Settings/Liedtke/My: Warning: Cannot stat: No such file or directory. tar: Documents/Tasks/Backup/rename.sh: Warning: Cannot stat: No such file or directory I've devised a workaround by copying the script to the PWD previous to the tar command and then deleting it. But it should work as above, correct? I've searched for the problem on the web and found nothing. Am I missing something obvious, or is this switch not handling embedded spaces in the path name correctly? (Thank you Microsoft.) Brian Liedtke -- 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/