Re: Bug #6778 Updated: fsockopen: timeout does not work when nameserver unreachable

I don't think we do this anywhere. I've thought of doing it, but I'm not at all sure what's the best way. Ideas anyone? Ideally it should be possible to specify the resolvers timeout but I haven't seen any good ways. Only other solutions I can think of are rather ugly using threads or maybe alarm(2)? Stig On Sun, Jul 22, 2001 at 01:56:37AM -0000, andy@php.net wrote: > ID: 6778 > Updated by: andy > Reported By: thomas@kipar.de > Status: Closed > Bug Type: Sockets related > Operating System: Debian 2.2 > PHP Version: 4.0.1pl2 > New Comment: > > Please upgrade to the latest version of PHP. Re-open if > still exists. > > Previous Comments: > ------------------------------------------------------------------------ > > [2001-07-21 21:55:50] andy@php.net > > Please upgrade to the latest version of PHP. Re-open if > still exists. > > ------------------------------------------------------------------------ > > [2000-09-16 16:20:46] thomas@kipar.de > > When doing a plain > fsockopen ("www.anyhost.com",$port,&$errno,&$errstr,$timeout) ... > and the nameserver for this host does not respond, is unreachable or at least extremely slow > (host www.anyhost.com produces 'A record not found'), fsockopen won't return after > $timeout (3secs for example)! > It hangs for at least 100-120 s. > > ------------------------------------------------------------------------ > > > > Edit this bug report at http://bugs.php.net/?id=6778&edit=1 > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net