php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #2995 connection_timeout uses ITIMER_PROF, not ITIMER_REAL
Submitted: 1999-12-17 16:40 UTC Modified: 1999-12-19 10:45 UTC
From: maxcom at vinchi dot ru Assigned:
Status: Closed Package: Feature/Change Request
PHP Version: 3.0.12 OS: RedHat Linux 6.1
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: maxcom at vinchi dot ru
New email:
PHP Version: OS:

 

 [1999-12-17 16:40 UTC] maxcom at vinchi dot ru 
PHP3 counts timeouts for scripts using ITIMER_PROF, but
following to documentation and my understanding of how
this should work, it must count time using ITIMER_REAL.
This is very important for database access pages that
does big database request. Normally user does not have rights to 
restart httpd or database server, so there are no way to
interrupt them or limit their execution time. This brings a lot
of problems to system administrators that has to abort
that stupid queries (that sometimes take too much system
resources). It seems that trivial replace of ITIMER_PROF/SIGPROF
to ITIMER_REAL/ALARM in main.c works file. I hope you will
change that or document in next version. Thank you for php3!

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [1999-12-19 10:45 UTC] rasmus at cvs dot php dot net 
Unfortunately it is not as simple as that.  Apache uses ITIMER_REAL/ALARM already.  The closest we can come is ITIMER_PROF/SIUGPROF.
The Apache request timeout should take care of queries that run for a long time.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sun May 19 12:01:30 2024 UTC