https://issues.apache.org/bugzilla/show_bug.cgi?id=51030
--- Comment #4 from Maxim <[email protected]> 2011-04-08 05:49:49 EDT --- (In reply to comment #3) > So to summarize, you would suggest; > > 1. send SIGTERM immediately > > 2. after timeout, send SIGKILL > > Is that what you are suggesting? > > As it can be harmful to some applications, I can only foresee this being > adopted as a per-dir (per specific <files > match) feature. Also be aware > that > httpd may not be aware until httpd attempts to send data that the remote > connection is AWOL, so this would be far from a perfect solution Not exactly... I mean the only situations when you precisely know that client leave (by pressing 'cancel browsing', for example), consequently there is no need to wait untill Timeout (cause nobody waits cgi-script output), and it would be good to inform cgi-script somehow about this to force it stopping some hard job (cause no one need the results of it) or some other finishing. Why not perfect? In opposite it'll be very usefull. Of cause it should be configurable per-dir behaviour. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
