Cyclone3 in mod_fastcgi vs mod_fcgid

Published 2007-09-15 in News by

FastCGI Status

Cyclone3 Framework runs fine with mod_fastcgi, but in most of GNU/Linux distributions (Gentoo, Debian) is this Apache module marked as obsolete or removed. It's because here is a new and compatible mod_fcgid and because for Apache 2.2.* is mod_fastcgi unstable solution.

That's okay, but here is one problem with mod_fcgid. I have it reported to fcgid developers, added into bugzilla's but without any answer.

Problem description:

Cyclone3 is using index script named core.tom in every one domain. Because this script is same in every domain, it's just a symlink to file /www/TOM/.core/tom3. When mod_fcgid receives request to fastcgi process, checks if it is not already running process. This check is based on script location, BUT tracks source of symlinks.

So, when I'm running two domains: domain.tld and localhost.tld which every has in !www directory symlink core.tom to /www/TOM/.core/tom, mod_fcgid thinks, it's the same process and for every domain returns same pages :)

Solution?

This problem can be solved by simple patch for mod_fcgid, but I can't say if mod_fcgid developers is responsible to commit our patch.

Updated: 2008-01-01

This problem has been solved by nice hack in tom3-update script (without need of patching mod_fcgid) available in development subversion repository (available in stable version soon).

AddThis Social Bookmark Button RSS