in reply to Re: mkdir() problem on windows
in thread mkdir() problem on windows

Windows permissions can be peculiar1, so it could be a problem with your security settings and such.

Nice theory, but either the OP is setting the permission explicitly, or he is inheriting them.

Were he setting them explicitly, we might assume that he might mention it.

If he is inheriting them, then creating a file within a subdirectory, will be subject to the same permissions as creating that directory within the CWD. Ie. If he can create the subdirectory, he'd be able to create a file within it.

Attributing this to "windows peculiar permissions" is ...

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^3: mkdir() problem on windows
by roboticus (Chancellor) on Nov 21, 2010 at 03:33 UTC

    BrowserUk:

    Yep, I mentioned it to him precisely because he may be inheriting some permissions he doesn't know about. I've been bitten by some odd Windows permissions in locked-down corporate environments, and nothing in the OP led me to believe that he was aware of those issues.

    ...roboticus

    Update: I think it may be possible to get that behaviour from the Windows permissions, but I'm by no means knowledgeable enough about them to state it with any certainty.

    Update: I've been reading the Icacls stuff posted, and it appears that if a directory had the AD privilege, but not the WD privilege, then they would be able to create a directory but not a file in that directory.

[reply]
      t appears that if a directory had the AD privilege, but not the WD privilege, then they would be able to create a directory but not a file in that directory.

      Not so. To the best of my ability to verify this--it's a pain to do--there is no combination of inherited ACLs that will allow you to create a directory and then not be able to create a file within that directory.

      The only circumstances I can envisage whereby this situation might come about without explicit setting of ACLs by the OP, is via Perl's emulation of the umask thing; or perhaps via cygwin's emulation of persistent umasks. But that all I can say on the subject as I'm not sufficiently conversant with the real thing to try and access whether the emulations are screwed or not.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom