Yes I think to him when say need a timeout procedure.
The Apache KILL is absolutely brutal and is better avoid to run in it
when there are connections to dbms or
opening of files.
Expecially if the procedure (qgis , processing, grass, and so on..) are
not think to work in a situation where
the work could be istantaneosly interrupted.
As example:
if apache kill a procedure that use grass.
The grass is istantaneosuly killed. And this mean it leave a lock file
in a own folder.
If an user don't remove it (the file) the grass don't restart correctly.
A.
Il 30/08/2014 13:58, Alessandro Pasotti ha scritto:
2014-08-30 13:28 GMT+02:00 aperi2007 <[email protected]>:
Another question could be the timeout.
Infact. If a processing take too much time to end.
It should go in timeout.
So not only concurrency need, but also a timeout system to avoid the lock
never ending of resources.
This is normally done at the webserver level:
http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#fcgidbusytimeout
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
