pqf wrote:
Hi, all
I am Ryan Pan, who wrote the first version of mod_fcgid.
While I uesd mod_fastcgi(not mod_fcgid), one issue that bother me is: while
a fastcgi process(created by mod_fastcgi's process manager process)in a dead
loop, no one is respond to kick it out. So from time to
2009/10/13 pqf p...@mailtech.cn:
Hi, all
I am Ryan Pan, who wrote the first version of mod_fcgid.
While I uesd mod_fastcgi(not mod_fcgid), one issue that bother me is: while
a fastcgi process(created by mod_fastcgi's process manager process)in a dead
loop, no one is respond to kick it
Jeff Trawick wrote:
maybe increasing the granularity of the lock could help
(multiple busy lists with the inode used as a hash to get to the
proper busy list)
I happen to have a module, unrelated to mod_fcgid, which manages
a fairly large shared-memory cache across a number of user
Chris Darroch wrote:
Because this runs on Linux and we're just using the APR defaults,
the process locks are SysV semaphores. Maybe sometime in the far
future, once glibc 2.10 appears on our systems, we might try
APR_LOCK_PROC_PTHREAD and see if we can't get the shiny new
Hi, all
I am Ryan Pan, who wrote the first version of mod_fcgid.
While I uesd mod_fastcgi(not mod_fcgid), one issue that bother me is: while a
fastcgi process(created by mod_fastcgi's process manager process)in a dead
loop, no one is respond to kick it out. So from time to time, some
