public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Create file fails on network drives in cygwin-1.7.9-1
Date: Fri, 17 Jun 2011 12:07:00 -0000	[thread overview]
Message-ID: <20110617120623.GC5087@calimero.vinschen.de> (raw)
In-Reply-To: <BANLkTikkb+ZUKT2J0y9HkjELBN0qu3ejKA@mail.gmail.com>

On Jun 17 12:36, Pete Forman wrote:
> On 17 June 2011 10:53, Corinna Vinschen wrote:
> > Btw., it would be an incredible good idea to change the permissions on
> > the remote drive to allow users to set or change the permissions of
> > files they created themselves.  Otherwise you end up with non-POSIX
> > permissions on the drive anyway, whether or not you're using "acl" or
> > "noacl" mount option.  If the network drives are not under your control,
> > try to persuade the admin.  If the admin is adamant, use the noacl mount
> > option for these drives.  You can also just change the cygdrive prefix
> > to use noacl on all drives.  See the User's Guide for how to do it.
> 
> I've just sat down with the admin and confirmed that I do have Full
> Control on the network drive. Creating and modifying files is working
> fine outside Cygwin.
> 
> chmod is failing with Permission denied in the same places that touch
> fails to create files.

There's still something disallowed.  If creating the file with ACL as
well as changing the ACL via chmod fails, then you don't have WRITE_DAC
permissions.  This has nothing to do with the permission to create
files, it's the permission you need to change permissions (aka to write
the file's DACL).  The error from opening the file in "acl" mode comes
only from this very problem.  If you use the "noacl" mount, then the
only difference when opening the file is that Cygwin does not requests
WRITE_DAC access.  It's not something in Cygwin itself, it's the
underlying Windows function which fails with "Access denied" in this
case.  The reason you can create files outside of Cygwin comes from the
simple fact that 99.999% of the non-Cygwin apps don't care for
permissions.  Cygwin does.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

  reply	other threads:[~2011-06-17 12:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 12:00 Pete Forman
2011-06-16 12:50 ` Corinna Vinschen
2011-06-16 14:31   ` Pete Forman
2011-06-16 14:59     ` Corinna Vinschen
2011-06-17  8:34       ` Pete Forman
2011-06-17  9:53         ` Corinna Vinschen
2011-06-17 11:36           ` Pete Forman
2011-06-17 12:07             ` Corinna Vinschen [this message]
2011-11-24  9:00 keith-kube
2011-11-24 10:03 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110617120623.GC5087@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).