running shell scripts

running shell scripts

[Steven Weiss]

Hi

/Develop/test/bin> chmod 755 work
/Develop/test/bin> ls -l work
-rwxr-xr-x    1 dbadmin Administ       27 Jun  9 20:18 work
/Develop/test/bin> ./work
bash: ./work: No such file or directory

I am trying to running a shell script from an interactive bash session. I
get the following error when running the shell script. It seems to work when
I put the #! /cygwin/bin/bash inside the script. Surely the script should
run with the execute permissions set as they are.

Regards
Steven
----------------------------------------
sweiss@iafrica.com
+27 21 7892985 (h)
+27 827715157 (m)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: running shell scripts

[Mathias Gygax]

On Mon, Jun 10, 2002 at 10:30:32AM +0200, Steven Weiss wrote:
> Hi

hi there,

> bash: ./work: No such file or directory
> 
> I am trying to running a shell script from an interactive bash
> session. I get the following error when running the shell script. It
> seems to work when I put the #! /cygwin/bin/bash inside the script.
> Surely the script should run with the execute permissions set as they
> are.

that's the way it works. the first shee-bang line topmost, is the
associated interpreter. it could be just anything, from a shell script
to awk program.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: running shell scripts

[wayne]

Or you could just do bash ./someprogram

On Mon, Jun 10, 2002 at 03:43:34PM +0200, Mathias Gygax wrote:
> On Mon, Jun 10, 2002 at 10:30:32AM +0200, Steven Weiss wrote:
> > Hi
> 
> hi there,
> 
> > bash: ./work: No such file or directory
> > 
> > I am trying to running a shell script from an interactive bash
> > session. I get the following error when running the shell script. It
> > seems to work when I put the #! /cygwin/bin/bash inside the script.
> > Surely the script should run with the execute permissions set as they
> > are.
> 
> that's the way it works. the first shee-bang line topmost, is the
> associated interpreter. it could be just anything, from a shell script
> to awk program.
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

-- 
Slowly and surely the unix crept up on the Nintendo user ...
Wayne Willcox                          I will not eat green eggs and ham
wayne@reliant.immure.com                     I will not eat them Sam I Am!!
A wise person makes his own decisions, a weak one obeys public opinion.
                -- Chinese proverb

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: running shell scripts

[Mathias Gygax]

On Mon, Jun 10, 2002 at 09:34:55AM -0500, wayne wrote:
> Or you could just do bash ./someprogram

or just

. someprogram

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: running shell scripts

[David T-G]

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

Mathias, et al --

...and then Mathias Gygax said...
% 
% On Mon, Jun 10, 2002 at 09:34:55AM -0500, wayne wrote:
% > Or you could just do bash ./someprogram
% 
% or just
% 
% . someprogram

Well, yes, but be careful about that, because you're then running the
script in the context of your shell instead of a subshell.  Any env vars
you change will stay changed, and if your shell ends with an exit then
your window will happily close.


HTH & HAND

:-D
-- 
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: running shell scripts

[Mathias Gygax]

On Mon, Jun 10, 2002 at 11:36:46AM -0500, David T-G wrote:
> % . someprogram
> 
> Well, yes, but be careful about that, because you're then running the
> script in the context of your shell instead of a subshell.  Any env vars
> you change will stay changed, and if your shell ends with an exit then
> your window will happily close.

well, what about

% (. someprogram)

:-D

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: running shell scripts

[David T-G]

[-- Attachment #1: Type: text/plain, Size: 689 bytes --]

Mathias --

...and then Mathias Gygax said...
% 
% On Mon, Jun 10, 2002 at 11:36:46AM -0500, David T-G wrote:
% > % . someprogram
% > 
% > Well, yes, but be careful about that, because you're then running the
...
% 
% well, what about
% 
% % (. someprogram)

Hmmm...  Yep, that sounds good.  Two more chars to type, though; it's
getting to be an awful lot of work ;-)


% 
% :-D


HAND

:-D
-- 
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: running shell scripts

[Larry Hall (RFK Partners, Inc)]

At 04:30 AM 6/10/2002, Steven Weiss wrote:
>Hi
>
>/Develop/test/bin> chmod 755 work
>/Develop/test/bin> ls -l work
>-rwxr-xr-x    1 dbadmin Administ       27 Jun  9 20:18 work
>/Develop/test/bin> ./work
>bash: ./work: No such file or directory
>
>I am trying to running a shell script from an interactive bash session. I
>get the following error when running the shell script. It seems to work when
>I put the #! /cygwin/bin/bash inside the script. Surely the script should
>run with the execute permissions set as they are.


bash is *not* the default shell in Cygwin.  /bin/sh is which is ash.  Did
you install it and make sure that it's in your path?

BTW, there's nothing wrong with providing the command interpreter as the 
first line of the script.  Actually, it's highly recommended practice.


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: running shell scripts

[David T-G]

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

Larry, et al --

...and then Larry Hall (RFK Partners, Inc) said...
% 
...
% 
% bash is *not* the default shell in Cygwin.  /bin/sh is which is ash.  Did

Hmmph.  I really do learn something new every day!

Now I guess I should go ahead and download ash, which I skipped originally
because I don't need fourteen different shells on the system to never
be used...


HAND

:-D
-- 
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: running shell scripts

[Earnie Boyd]

--- Bob McGowan <Robert.McGowan@veritas.com> wrote:
> Jens,
> 
> Check the scripts' first line, the #! one.  Be sure that it reference
> bash and that the path used is also correct.  
> As in:  #!/bin/bash
> 
> Be sure you have a /bin/bash.exe for the above to work.

Why bash instead of sh?  Sh is much more lightweight and faster to invoke!! 
That is the reason ash was used for sh.


=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32 >
    Mingw Home: (Coming Soon)
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: running shell scripts

[Jens Skakkebaek]

Hi,

It turned out that /bin was mounted wrongly.  Seems to semi-work now.  

Thanks for your help,

Jens

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

running shell scripts

[Jens Skakkebaek]

Hi,

I'm trying to run the Postgres database from cygwin and have got the main
database to work.
However, there a number of shell scripts that I cant run.  E.g., I get a "no
such file or directory" error when I tried to run some of the scripts. It
prints out the path correctly, so that's not the problem.

Prefixing it with the full path does not help.

Any pointers would be greatly appreciated.

Thanks in advance,

Jens Skakkebaek
jskakkebaek@adomo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: running shell scripts

[Bob McGowan]

Jens,

Check the scripts' first line, the #! one.  Be sure that it reference
bash and that the path used is also correct.  
As in:  #!/bin/bash

Be sure you have a /bin/bash.exe for the above to work.

If these are correct, try running one of the scripts using the
following:

   bash -x script_name 2>&1 | tee script_dbg.txt

Depending on where the failure happens, you will see various amounts of
output on the screen.  It should stop at the point where the problem
exists, hopefully providing a clue about what it is looking for.

Bob

Jens Skakkebaek wrote:
> 
> Hi,
> 
> I'm trying to run the Postgres database from cygwin and have got the main
> database to work.
> However, there a number of shell scripts that I cant run.  E.g., I get a "no
> such file or directory" error when I tried to run some of the scripts. It
> prints out the path correctly, so that's not the problem.
> 
> Prefixing it with the full path does not help.
> 
> Any pointers would be greatly appreciated.
> 
> Thanks in advance,
> 
> Jens Skakkebaek
> jskakkebaek@adomo.com
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: running shell scripts

[John Fortin]

> Hi,
>
> I'm trying to run the Postgres database from cygwin and have got the main
> database to work.
> However, there a number of shell scripts that I cant run.  E.g., I get a "no
> such file or directory" error when I tried to run some of the scripts. It
> prints out the path correctly, so that's not the problem.
>
> Prefixing it with the full path does not help.

If you post the script and/or show the session output when this happens, you are
much more likely to get
a helpful response.

John Fortin


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com