Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.1.0.6.0.20040611173122.03297f40@pop.prospeed.net>
X-Sender: 
Date: Fri, 11 Jun 2004 17:33:05 -0400
To: Rick Rankin <rick_rankin AT yahoo DOT com>, Cygwin <cygwin AT cygwin DOT com>
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Problem creating files on network drives with cygwin 1.5.10-3 and tar
In-Reply-To: <20040611210245.94854.qmail@web61008.mail.yahoo.com>
References: <20040611210245 DOT 94854 DOT qmail AT web61008 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 05:02 PM 6/11/2004, you wrote:
>After upgrading to 1.5.10, I'm seem to be having a problem creating files on
>network drives using tar. For quite a while now (a couple of years, at least),
>I've been using tar to back up several directories to a network share, and had
>no problems up through version 1.5.9. However, with 1.5.10-3, I get the message
>
>tar: /cygdrive/m/test.tar: Cannot open: No such file or directory
>tar: Error is not recoverable: exiting now
>
>when I issue the command
>
>tar -cf /cygdrive/m/test.tar test
>
>where test is a directory with a few files in it. 
>
>Now, it doesn't appear to be a permission problem as I can cd to /cygdrive/m
>and create files with touch or vim, delete files, copy files, etc. The network
>drives are hosted by Windows servers running either NT or 2K.
>
>I tried removing smbntsec from the CYGWIN env var, but that made no difference.
>I also tried the latest snapshot with the same results. Reverting to 1.5.9,
>however, fixes the problem. 
>
>I did try googling the mailing list archives, but most of what I found was
>related to accessing network shares after sshing to a remote node. 
>
>It appears to me that this might be related to 
>
>http://cygwin.com/ml/cygwin/2004-06/msg00014.html
>
>but I wasn't sure so I started a new thread.
>
>Cygcheck output attached. 
>


Maybe it's just me but there doesn't seem to by any cygcheck output.
Did you omit it inadvertently?

FWIW, a quick test with my nearest remote share did not reproduce the 
problem with cygwin 1.5.10.



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/