The problem is that I can't terminate dispatch.fcgi because my user does not own the associated processes.
It seems that the best way to give users control of fastcgi in a shared environment is to configure it with the autoupdate option, which will allow them to restart fastcgi by changing the modification time of dispatch.fcgi. If the users can't restart fastcgi then it's fairly useless because they'll not be able to change the application configuration without contacting eukhost to request a restart.
That's good news about mod_proxy, because it of course means that Mongrel can be used without displaying the port number in the URL. Thanks for that!
Can you configure fastcgi with the autoupdate option so that users have a choice of using Apache/fastcgi or Mongrel?
|