public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin 1.7.13-1: can't execute shell scripts on samba share
Date: Mon, 23 Apr 2012 11:54:00 -0000	[thread overview]
Message-ID: <20120423115331.GD7097@calimero.vinschen.de> (raw)
In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFCB@bespdc01.mediaxim.local>

On Apr 23 13:02, Michel Bardiaux wrote:
> [snip]
> 
> > lgiambro@lorien ~
> > $ cat len.sh
> > #!/bin/sh
> > echo it works
> 
> And man sh states " --norc Do  not  read  and  execute the personal
> initialization file ~/.bashrc if the
>               shell is interactive.  This option is on by default if the
> shell  is  invoked
>               as sh."
> Which eliminates bashrc as a possible culprit.
> 
> I have also tried the same as you did (len.sh on a samba share) and saw
> the same problem. Then I saw that the len.sh got a (cygwin *and* linux)
> mode of -rwxrw-r-- *without* doing any chmod. Then I saw that *every*
> file I create on the samba share, gets the same mode!
> 
> First things first, is there a workaround? Yes, chmod 777 len.sh *done
> on linux* works. And it actually works too when done on cygwin.
> 
> However, recreating len.sh on cygwin, then a chmod 700 len.sh again on
> cygwin, does not work, again "./len.sh: Permission denied". But the mode
> seen on the linux side is -rwx------.
> 
> I have also tried deleting then recreating the file in cygwin, then
> closing all cygwin processes and unmapping and remapping the samba
> drive. No cigar.
> 
> Then I tried cacls in various situations. It turns out that with mode
> 777, cacls reveals "Everyone:F", but with mode 700 we get:
> 
> len.sh <Account Domain not found>F
>               <Account Domain not found>(special access:)
>               Everyone:(special access:)
> 
> And getfacl says:
> 
> # file: len.sh
> # owner: ????????
> # group: ????????

You could mount the samba share with "noacl", see
http://cygwin.com/cygwin-ug-net/using.html#mount-table


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

  parent reply	other threads:[~2012-04-23 11:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 15:45 Len Giambrone
2012-04-18 17:49 ` Earnie Boyd
2012-04-18 19:45   ` Len Giambrone
2012-04-19  8:29     ` Michel Bardiaux
2012-04-20 17:44       ` Len Giambrone
2012-04-19 11:37     ` Earnie Boyd
2012-04-20 17:45       ` Len Giambrone
2012-04-23 11:02         ` Michel Bardiaux
2012-04-23 11:33           ` Earnie Boyd
2012-04-23 11:54           ` Corinna Vinschen [this message]
2012-04-23 12:26             ` Michel Bardiaux
2012-04-23 12:31               ` Corinna Vinschen
2012-04-23 12:44                 ` Michel Bardiaux
2012-04-23 12:29             ` Corinna Vinschen
2012-04-24 10:50           ` Andrey Repin
2012-04-24 12:15             ` Michel Bardiaux
2012-04-24 15:05               ` Andrey Repin
2012-04-24 15:20                 ` Michel Bardiaux
2012-04-24 17:20                   ` Andrey Repin
2012-04-26 14:18                     ` Michel Bardiaux
2012-04-26 18:50                       ` Andrey Repin

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=20120423115331.GD7097@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).