PhilFreak

Which is precisely why I'm trying to aggregate requests. I'd have thought that this would be such a frequent requirement that I'm surprised there isn't a ready-made solution.

Since you ask, the second process is to analyse the page requests for malicious activity and, if necessary, blacklist and report the remote ip.

I'm writing PHP in a web server environment behind nginx. When we receive a page request I want to issue a reply quickly and then start a timer. When the timer has expired I want to do some more work. Experiments with flush() were unfruitful so I split the work into two files and put this at the end of the first file: shell_exec("nohup php second.php $parameter 1> second.log 2> second.err"); The second file starts with a sleep() with the timeout set at around 60 seconds. It works but I really want to improve it by allowing the timer to be retriggered if another page request comes in so that second.php only runs once after all the page requests have been handled. Any ideas?