public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kevin_D'Elia@amsinc.com
To: cygwin@sourceware.cygnus.com
Subject: problems running shell scripts
Date: Fri, 07 Apr 2000 08:00:00 -0000	[thread overview]
Message-ID: <852568BA.0051B599.00@ams-central-gate-5a.amsinc.com> (raw)

Hello,

     I am trying to run some shell scripts under bash and all that happens is
that the shell scripts take a very long time to execute; when they finally
complete, all that shows up on stdout is the message "bash: <script_name> not
found"; both bash and the scripts are in the $PATH.  Has anyone else had this
problem?  I have tried putting sh.exe in /bin but that doesn't work,
     I should mention that, for other purposes, I have had to alter the
directory structure which is created during the Cygwin install so that it
reflects a more Un*x-like layout.  Specifically, I have the following:
     c:\usr\local\bin
     c:\usr\local\etc
     c:\usr\local\lib
     c:\usr\local\libexec
     c:\usr\local\man
     c:\usr\local\share

I have no problems with any other programs, diff, ls, all seem to work just
fine; only shell scripts won't run.  I have changed the magic number to point to
 /usr/local/bin instead of /bin, but that didn't help either.

Any help at all would be greatly appreciated, since I need to update some files
and would like to write some shell scripts to do this...



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

             reply	other threads:[~2000-04-07  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-07  8:00 Kevin_D'Elia [this message]
2000-04-07 12:03 Earnie Boyd

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=852568BA.0051B599.00@ams-central-gate-5a.amsinc.com \
    --to=kevin_d'elia@amsinc.com \
    --cc=cygwin@sourceware.cygnus.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).