public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Rainer Blome" <rainer.blome@gmx.de>
To: cygwin@cygwin.com
Subject: Re: chmod failed: Invalid argument
Date: Thu, 28 Jan 2016 15:43:00 -0000	[thread overview]
Message-ID: <trinity-f5aca8d9-16f5-41e1-a521-60beada36d8e-1453991058087@3capp-gmx-bs39> (raw)

(Apologies for not using the reply feature, I was not
subscribed when the last mail was sent. I am now subscribed.)

> Corinna Vinschen wrote:
> On Jan 28 01:27, Christopher Cobb wrote:
>> Or maybe chmod is broken, like it is on my machine:
>> $ chmod 777 x
>> chmod: changing permissions of âxâ: Invalid argument

> Can you please send the icacls output of the current directory and
> the icacls out for the file x?

Here are the icacls outputs for the test case:

$ umask
0027

$ mkdir bar
$ cd bar
$ icacls .
. hostname\username:(I)(OI)(CI)(F)

Successfully processed 1 files; Failed processing 0 files

$ touch foo
$ ls -la
total 0
drwx------+ 1 username 213 0 Jan 28 15:14 .
drwx------+ 1 username 213 0 Jan 28 15:14 ..
-rwx------  1 username 213 0 Jan 28 15:14 foo

$ icacls foo
foo hostname\username:(I)(F)

Successfully processed 1 files; Failed processing 0 files

$ icacls .
. hostname\username:(I)(OI)(CI)(F)

Successfully processed 1 files; Failed processing 0 files

--
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:[~2016-01-28 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 15:43 Rainer Blome [this message]
2016-01-28 16:11 ` Corinna Vinschen
2016-01-28 17:23   ` Aw: " Rainer Blome
2016-01-28 18:43     ` Corinna Vinschen
2016-01-28 20:18       ` Rainer Blome
2016-01-28 21:47         ` Corinna Vinschen
2016-01-31 22:45           ` Rainer Blome
2016-02-08 14:29             ` Corinna Vinschen
2016-02-10 10:59               ` Rainer Blome
2016-02-10 11:37                 ` 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=trinity-f5aca8d9-16f5-41e1-a521-60beada36d8e-1453991058087@3capp-gmx-bs39 \
    --to=rainer.blome@gmx.de \
    --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).