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

go to bug id or search bugs for

Bug #20380 stream_set_blocking() hangs
Submitted: 2002-11-11 22:31 UTC Modified: 2002-11-26 20:00 UTC
From: wweburg at maxis dot com Assigned:
Status: No Feedback Package: Filesystem function related
PHP Version: 4.2.3 OS: Linux Redhat, kernel 2.4
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
19 + 31 = ?
Subscribe to this entry?

 
 [2002-11-11 22:31 UTC] wweburg at maxis dot com 
When using stream_set_blocking() in place of either socket_set_blocking() or set_socket_blocking(), the script hangs. The call method is:

$fp = FSockOpen([valid connection data to internal network resource]);
stream_set_blocking($fp, FALSE);

The script operates normally when using socket_set_blocking, but complains via E_NOTICE error when set_socket_blocking is used, stating that it's deprecated and socket_set_blocking should be used. In the PHP manual, socket_set_blocking is an alias for stream_set_blocking. In the stream_set_blocking documentation, it states that both set_socket_blocking and socket_set_blocking are deprecated.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-11-11 22:38 UTC] wweburg at maxis dot com 
Not sure if this is filesystem related or socket related; changing category to sockets related.
 [2002-11-12 06:11 UTC] sniper@php.net 
Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip
 [2002-11-12 06:19 UTC] wez@php.net 
There is no stream_set_blocking() function in PHP 4.2.x.

Use socket_set_blocking() for 4.2; in 4.3 we are trying to
clean up namespace issues (as you have discovered, the naming of this function conflicts with the sockets extension), hence the name change.
 [2002-11-26 20:00 UTC] sniper@php.net 
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Apr 25 15:01:30 2024 UTC