|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #9676 Feature request for set_time_limit
Submitted: 2001-03-10 22:04 UTC Modified: 2010-11-24 09:02 UTC
From: tboothby at felfel dot com Assigned:
Status: Not a bug Package: *General Issues
PHP Version: 4.0.4pl1 OS: Red Hat Linux 6.2
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: tboothby at felfel dot com
New email:
PHP Version: OS:


 [2001-03-10 22:04 UTC] tboothby at felfel dot com
Taken from the user notes about set_time_limit()

"malhavoc at
23-Feb-2001 05:48 
I've noticed that using this function doesn't seem to block things that make calls to services and wait for a response. Setting set_time_limit(2) and then making a call to gethostbyaddr(ip.that.does.not.resolve) just sits there until it times out. 

It would be -really- nice if there was a perl-esque type function like alarm() that lets you set timeouts for specific sections of code, rather than entire scripts. I'd have great use for a feature that would enable me to run non crucial pieces of code for a few seconds, and then give up and move on if it takes too long."

This feature would be very nice.
Thanks for all your efforts,


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2010-11-24 09:02 UTC]
-Status: Open +Status: Bogus -Package: Feature/Change Request +Package: *General Issues
 [2010-11-24 09:02 UTC]
Same as bug #11592 which is better analyzed.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Jul 19 19:01:28 2024 UTC