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

go to bug id or search bugs for

Doc Bug #34706 Confusing socket_bind() documentation
Submitted: 2005-10-02 15:09 UTC Modified: 2005-10-02 16:51 UTC
From: garmoan at gmail dot com Assigned: simp (profile)
Status: Closed Package: Documentation problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: garmoan at gmail dot com
New email:
PHP Version: OS:

 

 [2005-10-02 15:09 UTC] garmoan at gmail dot com 
Description:
------------
As suggested by aidan to do...

The socket_bind() documentation could do with a couple extra lines to explain what it actually does.

i.e. socket_bind(), in terms of AF_INET, opens the port on the specified address, and in terms of AF_UNIX, creates the *.sock file for inter-process communication.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-10-02 15:34 UTC] simp@php.net 
Actually that's not what the function does. It assigns the address and port to a unbound socket. 
Opening the connection is still left for socket_listen or socket_connect.
 [2005-10-02 16:51 UTC] simp@php.net 
This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation better.

Binds the name given in address to the socket described by socket. This has to be done before a connection can be established using socket_connect or socket_listen.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Mon Jul 28 07:00:02 2025 UTC