public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Compiled Program System Calls Failing Code 127
Date: Tue, 17 May 2011 16:12:00 -0000	[thread overview]
Message-ID: <4DD29E42.4080508@cygwin.com> (raw)
In-Reply-To: <042e01cc1404$d8d7ae60$8a870b20$@gmail.com>

On 5/16/2011 4:07 PM, Leon Vanderploeg wrote:
> Greetings,
>
> I have a compiled C program that is installed on several servers.  It makes
> system calls to programs such as rsync, and has worked fine until now.  I
> recently installed it on two Server 2008R2 boxes, identical hardware.  Both
> are Cygwin 1.7.9.  C:\cygwin\bin is added to the Windows PATH variable on
> both machines.  The program runs fine on one box, but on the other box, the
> system calls return 127.
>
> http://cygwin.com/ml/cygwin/2006-08/msg00347.html says /bin/sh canÂ’t be
> found.  At the escalated command prompt, bash and sh start appropriate
> shells (although the which command points to /usr/bin/xxx) on both machines.
>
> Any idea what could be causing this behavior?

No, not really.  But I'd say it would be worth a look to see how the two
environments differ, including permissions.  cygcheck output from the two
machines might help you understand at least some of this.  If not, you may
have to do some debugging of the code on both machines to find the problem.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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:[~2011-05-17 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 20:07 Leon Vanderploeg
2011-05-17 16:12 ` Larry Hall (Cygwin) [this message]

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=4DD29E42.4080508@cygwin.com \
    --to=reply-to-list-only-lh@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).