From: "Lemke, Michael SZ/HZA-ZSW" <lemkemch@schaeffler.com>
To: <cygwin@cygwin.com>
Subject: RE: cygwin permissions problem on a network drive
Date: Fri, 21 Oct 2011 15:11:00 -0000 [thread overview]
Message-ID: <CC0D9E8456BA41488A76AFE4E8F3A3690278A8F0@de011305.de.ina.com> (raw)
In-Reply-To: <20111021143621.GD2976@calimero.vinschen.de>
On October 21, 2011 4:36 PM Corinna Vinschen wrote:
>On Oct 21 16:13, Lemke, Michael SZ/HZA-ZSW wrote:
>> On October 21, 2011 12:55 PM Corinna Vinschen wrote:
>> >On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote:
>> >> This is by design here. IT wants it that way.
>> >
>> >Then "noacl' is the only way for you.
>>
>> Unless I wait for the next release, right?
>
>No. If you don't want to get a "Permission denied" error messages every
>time some application tries to change the permissions, you will have to
>use "noacl". It seems you don't understand what "acl" vs. "noacl" is
>for. Does reading the User's Guide at
>http://cygwin.com/cygwin-ug-net/using.html#mount-table help?
No, that's not my problem. I am fine with the error message, it's
correct after all. The real problem with 1.7.9 is that I can't create
files although the permissions allow me to. And that seems to be fixed.
>
>> >Check with your admin and ask how they make sure that you can't set
>> >permissions. Did they just create a certain set of inheritable
>> >permissions or do they use some policy? That is what I'd like to know.
>>
>> I don't have a definitive answer yet but it looks like it's a
>> policy. In Windows Explorer I have Full Access for the top level
>> dir. That is inherited by every subdir and files. But the security
>> entry is greyed out, also for subdirs.
>
>Ok, so there is some sort of policy. It would be nice to get some
>"how to set up a share policy which doesn't allow changing permissions
> for dummies" :)
I'll see if I can get more from our admins.
Michael
next prev parent reply other threads:[~2011-10-21 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 12:52 Lemke, Michael SZ/HZA-ZSW
2011-10-20 22:58 ` gds
2011-10-21 8:50 ` Corinna Vinschen
2011-10-21 10:16 ` Lemke, Michael SZ/HZA-ZSW
2011-10-21 10:55 ` Corinna Vinschen
2011-10-21 14:14 ` Lemke, Michael SZ/HZA-ZSW
2011-10-21 14:37 ` Corinna Vinschen
2011-10-21 15:11 ` Lemke, Michael SZ/HZA-ZSW [this message]
2011-10-21 14:17 ` gds
2011-10-21 14:39 ` Corinna Vinschen
2011-10-21 16:32 ` gds
2011-10-21 17:34 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2012-01-04 14:25 Markus Leuthold
2012-01-09 13:52 ` Corinna Vinschen
2011-08-02 16:10 spambouncer
2011-08-02 20:54 ` Larry Hall (Cygwin)
2011-07-06 1:43 Bill Metzenthen
2011-07-06 6:31 ` Corinna Vinschen
2011-07-05 2:21 Bill Metzenthen
2011-07-05 8:59 ` Corinna Vinschen
2011-07-05 9:13 ` 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=CC0D9E8456BA41488A76AFE4E8F3A3690278A8F0@de011305.de.ina.com \
--to=lemkemch@schaeffler.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).