On 04/10/10 01:18, Juan J. Martínez wrote:
El lun, 04-10-2010 a las 01:11 +1100, David Taylor escribió:
On 03/10/10 21:33, Juan J. Martínez wrote:
El dom, 03-10-2010 a las 20:58 +1100, David Taylor escribió:
[...]
It does work from the command line. But when Cherokee does it, it fails.
I can see a difference. Cherokee uses /bin/sh -c exec ...
Any ideas how to debug what's going on in spawn-fcgi?
Can you paste the contents of spawn-fcgi?
Hi Juan,
It's a binary executable:
r...@hal:~# which spawn-fcgi
/usr/bin/spawn-fcgi
r...@hal:~# file /usr/bin/spawn-fcgi
/usr/bin/spawn-fcgi: symbolic link to `/etc/alternatives/spawn-fcgi'
r...@hal:~# file /etc/alternatives/spawn-fcgi
/etc/alternatives/spawn-fcgi: symbolic link to
`/usr/bin/spawn-fcgi.standalone'
r...@hal:~# file /usr/bin/spawn-fcgi.standalone
/usr/bin/spawn-fcgi.standalone: ELF 32-bit LSB executable, Intel 80386,
version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
2.6.18, stripped
r...@hal:~# dpkg -S /usr/bin/spawn-fcgi.standalone
spawn-fcgi: /usr/bin/spawn-fcgi.standalone
r...@hal:~#
Thanks Juan.
Cheers,
David.
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
