PHP script always executed at the background, if not mistaken.

I run my maintenance routine everytime I log in to my admin area. It will not affect my clients' site and yet keep my database clean. I log in at least once a week and did not notice any delay or slow down. I think you can do the same.

If you are working in a webserver you have full access to, you can also setup a cronjob!

But be aware, that your code should log errors and message to logfiles instead of the console.

Thanks guys

I was just hoping of an idea to run a php script initiated by a visitor where a user wouldnt have to wait for the whole maintenance execution. I guess kind of like branching a single process into two. Thats something I havent done before; Im not sure if its possible.

How about you have a cron job but you also have it so that it can be run from the browser or from the shell. Do you need it running all the time?

Have a look at the PsExec tools (google it). With it you can run an external program, and choose to wait for it. This could do what you need.

Hi,

What you could do is use the exec() function in PHP that always to to execute shell commands. (Also see: popen, and proc_open() )

You can use the & option to run the command in the background.

Example:

[PHP]
<?php
exec( 'wget http://www.example.com/file.php > /dev/null &' );
?>
[/PHP]

The > /dev/null sends your php output to nowhere.
The & makes the wget run in the background.

You can use other commands rather than wget, but thats one Im sure of the syntax for.

If you cant use exec() then you could try using the HTTP protocol to your advantage to fork your php script for you.

I havent tested but I believe if you could do something like:

[PHP]
header( 'Location : http://www.example.com/new_file.php' );
echo str_pad(' ', 256); // make IE start rendering
flush();

// Do your other stuff here, in the background
// The browser is now fetching http://www.example.com/new_file.php
// Make sure you dont output anything

run_my_maintanence();

[/PHP]

I believe this will work.
For IE to actually start following the HTTP headers, it has to receive at least 256 bytes of content.. (now why?)

See if either of those work for you.

PHP does always run in the background it is server side scripting. something like javascript which is client side would run in the foreground.

I've posted an entry about this in my blog. if you are interested check out:
http://fijiwebdesign.com/content/view/86/77/

impressive wget option. I wasn't aware of that

Sorry for not clarifying: run in the background I meant run as a separate process which will not be a bottleneck for the main process.

Thanks very much
tim