X-Spam-Check-By: sourceware.org Date: Wed, 11 Jul 2007 08:31:08 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: "kavitha Bhasker -X (kbhasker - Infosys AT Cisco)" cc: cygwin AT cygwin DOT com Subject: Re: Cygwin tar1.16.1 - stdout/stdin behaviour on windows In-Reply-To: <8EB00AB9BCE95E4DBADDDB25EBCBF95D037DA0B7@xmb-blr-418.apac.cisco.com> Message-ID: References: <8EB00AB9BCE95E4DBADDDB25EBCBF95D037DA0B7 AT xmb-blr-418 DOT apac DOT cisco DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Tue, 10 Jul 2007, kavitha Bhasker -X (kbhasker - Infosys AT Cisco) wrote: > Hi, > > Iam using the Cygwin Tar version 1.16.1 on an Windows NT Server , I have > the following dll's copied to the same path as the tar.exe > From cygwin/1.5.24-2 : cygiconv-2.dll cygintl-8.dll > cygwin1.dll > > Iam able to run the command : tar --forcelocal -cvf C:\\temp.tar > C:\\temp successfully. > > However, the program I run , needs to do something more complicated like > : > > 1) tar -cvf - C:\\temp + Use Maverick J2SSH library to SFTP files from > stdout to stream the tar file to the SFTP location > > and to later restore the files: > > 2) Use Maverick J2SSH library to SFTP files to stdin the tar file from > the SFTP location + tar -xv - > > This works in Linux RH4.0 , when I use the standard /bin/tar . However, > just does not seem to work on Windows using the Cygwin Tar.exe > > Command 1) works and am able to see the tar getting created on the SFTP > location. > > However, am not able to tar -tvf on the file.Just gives blank response. > I cannot even open the .tar file created using winzip. Says Invalid Tar > file > > Command 2) Just does not see to like stdin and refuses to extract the > file to the local directory > > Please help.Is there any known issue with cygwin tar and stdout/stdin > behaviour on windows? Everything Eric said about copying the DLLs being unsupported, the old version of tar, and about using Win32 paths stands. Expanding on that, however, you seem to have omitted the --forcelocal option in your two non-working examples, which may cause tar to look at a remote filesystem (and time out, I guess). I would first try POSIX paths. If that doesn't help, please look at for guidelines on reporting Cygwin problems. In particular, you might want to clarify the "Just does not see to like stdin" part (i.e., what exactly happens?), and what the output looks like for the first command (you *are* running "tar -cvf", after all). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Belief can be manipulated. Only knowledge is dangerous. -- Frank Herbert -- 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/