[#9722] Kernel#system broken inside Dir.chdir(&block) if system command doesn't have shell characters — <noreply@...>

Bugs item #7278, was opened at 2006-12-14 13:59

8 messages 2006/12/14

[#9749] System V IPC in standard library? — Steven Jenkins <steven.jenkins@...>

Back in August, I needed a semaphore to serialize access to an external

14 messages 2006/12/19

[#9753] CVS freeze — SASADA Koichi <ko1@...>

Hi,

20 messages 2006/12/20
[#9755] Re: [ruby-dev:30039] CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

[#9757] Re: [ruby-dev:30040] Re: CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

Re: [ ruby-Bugs-7278 ] Kernel#system broken inside Dir.chdir(&block) if system command doesn't have shell characters

From: "Jim Helm" <perlguy@...>
Date: 2006-12-15 05:08:00 UTC
List: ruby-core #9728
Sounds like the difference betwen exec and /bin/sh running p4 could still be
the cause...

Try this, and see if there's anything missing from the bare "env" output
that's present in the "env;" output that might affect perforce.

ruby -e 'system("env")'
ruby -e 'system("env;")'

I bet you'll find an env var that's maybe in .bashrc or the like, that isn't
sourced when ruby uses /bin/sh to run the script.

--
Jim


On 12/14/06, Eric Hodel <drbrain@segment7.net> wrote:
>
> On Dec 14, 2006, at 18:57, Michael Selig wrote:
> > I bet your script /usr/local/bin/p4 is a shell script which doesn't
> > have a
> > "#!/bin/sh" line at the top, and that if you put one in, it will
> > work in
> > both cases.
>
> Nope.
>
> $ file /usr/local/bin/p4
> /usr/local/bin/p4: Mach-O executable i386
>
> --
> Eric Hodel - drbrain@segment7.net - http://blog.segment7.net
>
> I LIT YOUR GEM ON FIRE!
>
>
>

In This Thread