On 04/19/2011 09:03 AM, Hajo Locke wrote:
You could issue a "kill " of your fcgi-wrapper process that
handles your specific vhost
Do you have often trouble with your users when killing the processes or
are these killings barely noticeable?
I don't, but i think that is highly dependant on wha
Hello,
You could issue a "kill " of your fcgi-wrapper process that handles
your specific vhost (i distinguish mine through the use of different users
via suexec, so i can do a "pkill -u "), apache will spawn a new
process when it recieves the next request. However, note that this is not
grace
I am not very familiar with mod_fcgid, but hat you want is possible with
what I am running:
httpd 2.3.12-dev with mod_proxy_fcgi
PHP 5.3.7-dev with php-fpm
interesting, but not an option for productive systems.
the killing of user-processes, like suggested by Björn, also isnt a nice
solution b
On April 13, 2011 4:00 , "Hajo Locke" wrote:
is there a possibility to reload a separate fcgid-application
(mod_fcgid) if something has changed?
May be the php.ini for my wrapper-script has changed and i want to
reload this application for vhost without disturbing other apps.
Is this possible
On 04/13/2011 10:00 AM, Hajo Locke wrote:
is there a possibility to reload a separate fcgid-application
(mod_fcgid) if something has changed?
Hi,
You could issue a "kill " of your fcgi-wrapper process that handles
your specific vhost (i distinguish mine through the use of different
users via
Hello,
is there a possibility to reload a separate fcgid-application (mod_fcgid) if
something has changed?
May be the php.ini for my wrapper-script has changed and i want to reload
this application for vhost without disturbing other apps.
Is this possible? I think a reload of apache stops all f
