Date: Fri, 24 Dec 2004 08:51:13 -0600
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: pygopherd & scriptexec
Message-ID: <20041224145113.GC4277@katherina.lan.complete.org>
References: <41CB7DA7.6090608@aaronjangel.us>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41CB7DA7.6090608@aaronjangel.us>
User-Agent: Mutt/1.5.6+20040907i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Thu, Dec 23, 2004 at 08:23:35PM -0600, Aaron J. Angel wrote:
> I'm trying out this scriptexec stuff in pygopherd, but I get an error:
> 
>    File "/usr/lib/python2.2/site-packages/pygopherd/pipe.py", line 43, in
> pipedata_unix

That line is:

            os.execve(file, args, environ)

I might suggest running strace -f on the pygopherd process to see just
what it is trying to exec.  That would be a useful first step anyway.

Oh, if you're running chroot -- you likely have no /bin in your
chroot, let alone a /bin/sh.

-- 
John Goerzen
Author, Foundations of Python Network Programming
http://www.amazon.com/exec/obidos/tg/detail/-/1590593715