X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.1 required=5.0	tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;	charset="utf-8"
Subject: RE: cygwin permissions problem on a network drive
Date: Fri, 21 Oct 2011 12:15:29 +0200
Message-ID: <CC0D9E8456BA41488A76AFE4E8F3A3690278A577@de011305.de.ina.com>
In-Reply-To: <20111021085010.GF13505@calimero.vinschen.de>
References: <CC0D9E8456BA41488A76AFE4E8F3A36902731CC0 AT de011305 DOT de DOT ina DOT com> <j7q925$5sd$1 AT dough DOT gmane DOT org> <20111021085010 DOT GF13505 AT calimero DOT vinschen DOT de>
From: "Lemke, Michael  SZ/HZA-ZSW" <lemkemch AT schaeffler DOT com>
To: <cygwin AT cygwin DOT com>
X-SEF-7853D99-ADF1-478E-8894-213D316B8FFA: 1
X-SEF-Processed: 7_3_0_01170__2011_10_21_12_15_30
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id p9LAG5cx012527

On Friday, October 21, 2011 10:50 AM
Corinna Vinschen wrote:
>
>On Oct 20 18:58, gds wrote:
>> On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
>> 
>> >
>> >I know this an old thread but I am in exactly the same situation as
>> >the OP.  Access with 1.7.7 and before worked fine, 1.7.9 has this
>> >problem.  The workaround with explicit noacl option works for me but
>> >it is rather awkward as I have to work with a lot of servers.
>> >
>> >So...
>> >
>> 
>> >
>> >...has this happened now?  In a snapshot?  I couldn't find any
>> >further information.

So from the reply below I take it hasn't been fixed/worked
around in a snapshot.  But my experiments show something has
changed.  With the snapshot I can create a file, with the standard
1.7.9 dll I can't.
 
>> 
>> Same problem here. Someone said snapshots here,
>> http://cygwin.com/snapshots/ , fixes the problem but I tried several
>> cygwin1.dll from there and still have problems.
>> Directory is created on network drive now but see message "can't set
>> permissions ... on a file" when committing with svn.
>
>I explained what the problem is already.  The buzzword is WRITE_DAC.
>Apparently you don't have permissions to change file permissions 
>on that share.  Cacls should show the exact layout of the file and
>directory DACLs.  Does `chmod' work for you?  It shouldn't either.

In my case that it true, chmod fails.

>
>You could talk to your admin first to find out if that is by design and
>maybe there could be something changed to allow changing permissions.

This is by design here.  IT wants it that way.

>Otherwise, just mount the share with the noacl flag.
>
>Again, I don't know why this happens.  I can not reproduce this problem
>on my NTFS shares, other than by removing the WRITE_DAC permission from
>the affected files and directories.  If there's any way to fix or
>workaround it in Cygwin, somebody who has that problem has to hunt it
>down.
>

I am willing to try to hunt it down.  What do you want me to check?
Hm, it seems something really has changed, I can't reproduce the
problem at the moment.  I can create a file, delete it but can’t
change permissions.  The latter breaks d2u:

$> touch /u/blubb
$> d2u /u/blubb
dos2unix: Failed to change the permissions of temporary output file /u/d2utmpaF6gvB: Permission denied
dos2unix: converting file /u/blubb to Unix format ...
dos2unix: problems converting file /u/blubb
$> rm /u/blubb
rm: remove regular empty file `/u/blubb'? y
$>

Is there anything in the snapshot that could explain it?  Or
did I mess up everything here?  Confused...

Well, I just cross checked.  Reinstalled 1.7.9 and the problem
is back.  So the snapshot seems to have fixed it.  That is,
this snapshot:
CYGWIN_NT-5.1 p01080268 1.7.10s(0.253/5/3) 20111017 18:26:05 i686 Cygwin
Didn't try the latest.  With the snapshot it behaves like 1.7.7 apparently.

Michael