Differences between version 2 and previous revision of getsockname(2).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, December 31, 2002 2:10:03 am | by PerryLorier | Revert |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:23:41 am | by perry | Revert |
@@ -1,84 +1,27 @@
-GETSOCKNAME
-!!!GETSOCKNAME
-NAME
-SYNOPSIS
-DESCRIPTION
-RETURN VALUE
-ERRORS
-CONFORMING TO
-NOTE
-SEE ALSO
-----
!!NAME
+getsockname - get socket name
-
-getsockname - get socket name
!!SYNOPSIS
+ __#include <sys/socket.h>__
-
-__#include __
-
-
-
-
+
__int getsockname(int s , struct sockaddr * name , socklen_t * namelen )__
!!DESCRIPTION
+getsockname(2) returns the current ''name'' for the specified socket. The ''namelen'' parameter should be initialized to indicate the amount of space pointed to by ''name''. On return it contains the actual size of the name returned (in bytes).
-
-__Getsockname__ returns the current ''name'' for the
-specified socket. The ''namelen'' parameter should be
-initialized to indicate the amount of space pointed to by
-''name''. On return it contains the actual size of the
-name returned (in bytes).
!!RETURN VALUE
+On success, zero is returned. On error, -1 is returned, and ''errno'' is set appropriately.
-
-On success, zero is returned. On error, -1 is returned, and
-''errno'' is set appropriately.
!!ERRORS
+;[EBADF]: The argument ''s'' is not a valid descriptor.
+;[ENOTSOCK]: The argument ''s'' is a file, not a socket.
+;[ENOBUFS]: Insufficient resources were available in the system to perform the operation.
+;[EFAULT]: The ''name'' parameter points to memory not in a valid part of the process address space.
-
-__EBADF__
-
-
-The argument ''s'' is not a valid
-descriptor.
-
-
-__ENOTSOCK__
-
-
-The argument ''s'' is a file, not a socket.
-
-
-__ENOBUFS__
-
-
-Insufficient resources were available in the system to
-perform the operation.
-
-
-__EFAULT__
-
-
-The ''name'' parameter points to memory not in a valid
-part of the process address space.
!!CONFORMING TO
+SVr4, 4.4BSD (the getsockname(2) function call appeared in 4.2BSD). SVr4 documents additional [ENOMEM] and [ENOSR] error codes.
-
-SVr4, 4.4BSD (the __getsockname__ function call appeared
-in 4.2BSD). SVr4 documents additional ENOMEM and ENOSR error
-codes.
!!NOTE
+The third argument of getsockname(2) is in reality an `int *' (and this is what BSD 4.* and libc4 and libc5 have). Some POSIX confusion resulted in the present socklen_t. The draft standard has not been adopted yet, but glibc2 already follows it and also has socklen_t. See also accept(2).
-
-The third argument of __getsockname__ is in reality an
-`int *' (and this is what BSD 4.* and libc4 and libc5 have).
-Some POSIX confusion resulted in the present socklen_t. The
-draft standard has not been adopted yet, but glibc2 already
-follows it and also has socklen_t. See also
-accept(2).
!!SEE ALSO
-
-
bind(2), socket(2)
-----
