Hello All,
A very simple question today, but one who's answer could prove quite useful. Is there a way to capture when a script is killed because of a browser timeout? I have a script that could potentially run for a very long time and I'd like to politely tell people that a browser timeout has happened, inside the error log, as well as a few words of wisdom (of my own) on how to prevent the problem in the future.
I know there are all kinds of signals out there, but it's somewhat of a more low level function that this poor CGI scripter hasn't had much meditation on.
For extra points, the potential browser timeout function is inside a child process that's forked() off from the parent. I'm thinking that it would actually be easier to capture that signal.
Could anyone offer some insight?
Always appreciative,
-justin simoni
!skazat!
In reply to Capturing a Browser Timeout Signal by skazat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |