HP-UX Reference (11i v1 00/12) - 2 System Calls (vol 5)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man2/!!!intro.2
________________________________________________________________
___ ___
g
getsockopt(2) getsockopt(2)
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)).
MULTITHREAD USAGE
The getsockopt() and setsockopt() system calls are thread-safe. They each have a cancellation
point; and they are async-cancel safe, async-signalsafe, and fork-safe.
AUTHOR
getsockopt() and setsockopt() were developed by HP and the University of California, Berkeley.
SEE ALSO
socket(2), getprotoent(3N), af_ccitt(7F), tcp(7P), udp(7P), unix(7P), xopen_networking(7).
STANDARDS CONFORMANCE
getsockopt() : XPG4
Section 2−−116 − 5 − HP-UX Release 11i: December 2000
___
___