getsockname.2 (2010 09)

g
getsockname(2) getsockname(2)
such migration problems. On the other hand, applications that need to be portable to the UNIX 95 profile
should follow the X/Open specification (see xopen_networking(7)).
WARNINGS
Linking binary objects compiled to X/Open Sockets specification and binary objects compiled to HP-UX
BSD Sockets specification to the same executable may result in unexpected behavior, including applica-
tion abnormal termination and unexpected socket errors. See xopen_networking(7) for details and
remedy.
FUTURE DIRECTION
Currently, the default behavior is the HP-UX BSD Sockets; however, it might be changed to X/Open
Sockets in a future release. At that time, any HP-UX BSD Sockets behavior that is incompatible with
X/Open Sockets might be obsoleted. Applications that conform to the X/Open specification now will
avoid migration problems (see xopen_networking(7)).
AUTHOR
getsockname()
was developed by HP and the University of California, Berkeley.
SEE ALSO
bind(2), socket(2), getpeername(2), thread_safety(5), inet(7F), xopen_networking(7).
STANDARDS CONFORMANCE
getsockname(): XPG4, UNIX 95, UNIX 03
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010