public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Len Giambrone <Len.Giambrone@intersystems.com>
To: Michel Bardiaux <MBardiaux@mediaxim.be>
Cc: "<cygwin@cygwin.com>" <cygwin@cygwin.com>
Subject: Re: cygwin 1.7.13-1: can't execute shell scripts on samba share
Date: Fri, 20 Apr 2012 17:44:00 -0000	[thread overview]
Message-ID: <F3BCC570-26AD-4710-8612-F6D366E9EA57@intersystems.com> (raw)
In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802EC895B@bespdc01.mediaxim.local>



-Len




On Apr 19, 2012, at 4:29 AM, Michel Bardiaux wrote:

> 2 suggestions:
> 
> 1. What happens if len.sh is in your Cygwin home, that is on the local
> drive?

lgiambro@lorien ~
$ ./len.sh
it works

> 
> 2. What happens with "sh -x ./len.sh" (on the network drive)?
> 

lgiambro@lorien //kitserver/kits
$ sh -x ./len.sh
+ echo it works
it works


> HaND,
> 
> -----Original Message-----
> 
> No.  That works.  presumably because it's executing "bash" and not the
> script itself.
> 
> -Len
> 
> 
> 
> 
> On Apr 18, 2012, at 1:49 PM, Earnie Boyd wrote:
> 
>> On Wed, Apr 18, 2012 at 11:44 AM, Len Giambrone 
>> <Len.Giambrone@intersystems.com> wrote:
>>> I'm can't execute shell scripts on a samba share served by our linux
> boxes.
>>> 
>>> lgiambro@lorien //kitserver/kits
>>> $ ls -la len.sh
>>> -rwx------ 1 lgiambro releng 24 Apr 18 10:48 len.sh
>>> 
>>> lgiambro@lorien //kitserver/kits
>>> $ cat len.sh
>>> #!/bin/sh
>>> echo it works
>>> 
>>> lgiambro@lorien //kitserver/kits
>>> $ ./len.sh
>>> -bash: ./len.sh: Permission denied
>> 
>> I suppose the same happens if you execute len.sh similar to the
> following?
>> 
>> $ bash -x ./len.sh
>> 
> 
> --
> 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
> 


--
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:[~2012-04-20 17:44 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 [this message]
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
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=F3BCC570-26AD-4710-8612-F6D366E9EA57@intersystems.com \
    --to=len.giambrone@intersystems.com \
    --cc=MBardiaux@mediaxim.be \
    --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).