Ticket #1452 (new defect)

Opened 8 months ago

Last modified 6 months ago

spawn-fcgi doesn't pass on the exit code from child's it spawns

Reported by: glen Assigned to: jan
Priority: normal Milestone: 1.4.20
Component: core Version: 1.4.18
Severity: normal Keywords:
Cc: Blocking:
Need Feedback: 0

Description 

# /usr/sbin/spawn-fcgi -P /var/run/php-fcgi.pid -u http -g http -s /var/run/php/fcgi.sock.1wrOTB -f /usr/bin/php.fcgi -C 8
sh: /usr/bin/php.fcgi: not found
spawn-fcgi.c.207: child exited with: 127, Unknown error 127
# echo $?
0

Attachments

Change History

01/29/2008 11:13:27 AM changed by mpo@newtec.eu

It is not only spawn-fcgi that displays wrong behavior. lighttpd itself has the same behavior:

root:~# /usr/sbin/lighttpd -f /etc-ro/lighttpd/lighttpd.conf 2008-01-29 11:07:35: (mod_fastcgi.c.900) bind failed for: unix:/var/run/lighttpd/php-fastcgi.socket-0 No such file or directory 2008-01-29 11:07:35: (mod_fastcgi.c.1336) [ERROR]: spawning fcgi failed. 2008-01-29 11:07:35: (server.c.895) Configuration of plugins failed. Going down. root:~# echo $? 0 root:~#

This behavior makes writing a proper start/stop scripts a pain in the *ss

Add/Change #1452 (spawn-fcgi doesn't pass on the exit code from child's it spawns)




Change Properties