Hello Everyone,

I'm running a website building/management system (http:// habitatlife.com/) using an apache2/mod_perl2 via unix platform and want to run some time consuming
processes without tying up my apache/mod_perl children.

Ideally, I would run these programs then continue on with returning feedback, etc. without waiting for the program to complete, checking on the status of the operation with a different "quick check" request, like flagging the database or something from the program with feedback, "beginning, error, done, etc", then checking the status
intentionally.

What is the safest approach to accomplish this. Its running on a dedicated server and for now I'm only planning on running programs on the same server, i.e. local
to the apache/mp2 build.

In particular, what syntax/mod should be used to assure the program gets run securely
from mod_perl?
(e.g. running a perl script that does a whole site backup)

TIA,
Boysenberry Payne

Reply via email to