X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=3.0 required=5.0 tests=BAYES_00,TW_PV,WEBMAIL_BODY
X-Spam-Check-By:	sourceware.org
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	Av0EAF3EzU7SD90n/2dsb2JhbABABKp2gQWBcgEBBDMBSxYNBAMBAgo0QCEbh2oIlGqfToNfg10RgxUEmieMPw
Message-ID:	<1322108117.4ecdc4d5759fe@webmail.netspace.net.au>
Date:	Thu, 24 Nov 2011 15:15:17 +1100
From:	keith-kube AT netspace DOT net DOT au
To:	cygwin AT cygwin DOT com
Subject:	Re: Create file fails on network drives in cygwin-1.7.9-1
MIME-Version:	1.0
User-Agent:	Internet Messaging Program (IMP) 3.2.1
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

I had the same problem, and the suggested solution below worked.

Failing a permanent fix, it would be great if a future version of cygwin allowed
me to specify (via a config file) that I need to mount (some or all) of the
/cygdrive directories with noacl option (or even better - pointers on how to
achieve that with the current version).  In the meantime I have set up
/etc/fstab as specified below and modified our scripts to write to the manually
mounted network share.

We have deliberately weird permissions on some directories, so I am unlikely to
be able to convince either auditors or system administrators to modify the setup

$ uname -a
CYGWIN_NT-5.2 awmspvw00204 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin

> Date: Thu, 16 Jun 2011 16:58:34 +0200
> From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
> To: cygwin at cygwin dot com
> Subject: Re: Create file fails on network drives in cygwin-1.7.9-1
> Message-ID: <20110616145834 DOT GA21703 AT calimero DOT vinschen DOT de>
> References: <BANLkTim75avYGKmYhzzdEmbqjt5Dfu1WNg AT mail DOT gmail DOT com> 
> <20110616124954 DOT GY12140 AT calimero DOT vinschen DOT de> 
> <BANLkTin1t2DZedqY7TBWDbPAW_ra=oiuzg AT mail DOT gmail DOT com>
> In-Reply-To: <BANLkTin1t2DZedqY7TBWDbPAW_ra=oiuzg at mail dot gmail 
> dot com>

>Thanks.  AFAICS the permissions on that network drive don't allow a 
>user to set the ACL of a file he or she's just creating.  In contrast 
>to previous versions, Cygwin 1.7.9 requests the permission for that 
>right at file creation time.  Unfortunately that fails due to the weird 
>permission settings on that drive.
>
>Try to mount your drive with the noacl option to some arbitrary mount 
>point, for instance:
>
>  mount -f -o noacl,binary X: /my_x_drive
>
>and then use the path below that mount point to access the drive.
>
>If that works, you can add the path to your personal fstab file (see 
>http://cygwin.com/cygwin-ug-net/using.html#mount-table):
>
>  X: /my_x_drive none noacl,binary,posix=0 0 0
>
>Please report back if it helped.  If so, I'll add some workaround for 
>this problem to the next Cygwin version.

>Corinna
 




------------------------------------------------------------
This email was sent from Netspace Webmail: http://www.netspace.net.au


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -