logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

sys_un.h.0p (3108B)

    

  1. '\" et
  2. .TH sys_un.h "0P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. sys/un.h
  12. \(em definitions for UNIX domain sockets
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. #include <sys/un.h>
  17. .fi
  18. .SH DESCRIPTION
  19. The
  20. .IR <sys/un.h> 
  21. header shall define the
  22. .BR sockaddr_un
  23. structure, which shall include at least the following members:
  24. .sp
  25. .RS 4
  26. .nf
  28. sa_family_t  sun_family  \fRAddress family.\fR
  29. char         sun_path[]  \fRSocket pathname.\fR
  30. .fi
  31. .P
  32. .RE
  33. .P
  34. The
  35. .BR sockaddr_un
  36. structure is used to store addresses for UNIX domain sockets.
  37. Pointers to this type shall be cast by applications to
  38. .BR "struct sockaddr *"
  39. for use with socket functions.
  40. .P
  41. The
  42. .IR <sys/un.h> 
  43. header shall define the
  44. .BR sa_family_t
  45. type as described in
  46. .IR <sys/socket.h> .
  47. .LP
  48. .IR "The following sections are informative."
  49. .SH "APPLICATION USAGE"
  50. The size of
  51. .IR sun_path
  52. has intentionally been left undefined. This is because different
  53. implementations use different sizes. For example, 4.3 BSD uses a size of
  54. 108, and 4.4 BSD uses a size of 104. Since most implementations
  55. originate from BSD versions, the size is typically in the range 92 to
  56. 108.
  57. .P
  58. Applications should not assume a particular length for
  59. .IR sun_path
  60. or assume that it can hold
  61. {_POSIX_PATH_MAX}
  62. bytes (256).
  63. .P
  64. Although applications are required to initialize all members
  65. (including any non-standard ones) of a
  66. .BR sockaddr_in6
  67. structure (see
  68. .IR "\fB<netinet_in.h>\fP"),
  69. the same is not required for the
  70. .BR sockaddr_un
  71. structure, since historically many applications only initialized
  72. the standard members. Despite this, applications are encouraged
  73. to initialize
  74. .BR sockaddr_un
  75. structures in a manner similar to the required initialization of
  76. .BR sockaddr_in6
  77. structures.
  78. .SH "RATIONALE"
  79. None.
  80. .SH "FUTURE DIRECTIONS"
  81. None.
  82. .SH "SEE ALSO"
  83. .IR "\fB<netinet_in.h>\fP",
  84. .IR "\fB<sys_socket.h>\fP"
  85. .P
  86. The System Interfaces volume of POSIX.1\(hy2017,
  87. .IR "\fIbind\fR\^(\|)",
  88. .IR "\fIsocket\fR\^(\|)",
  89. .IR "\fIsocketpair\fR\^(\|)"
  90. .\"
  91. .SH COPYRIGHT
  92. Portions of this text are reprinted and reproduced in electronic form
  93. from IEEE Std 1003.1-2017, Standard for Information Technology
  94. -- Portable Operating System Interface (POSIX), The Open Group Base
  95. Specifications Issue 7, 2018 Edition,
  96. Copyright (C) 2018 by the Institute of
  97. Electrical and Electronics Engineers, Inc and The Open Group.
  98. In the event of any discrepancy between this version and the original IEEE and
  99. The Open Group Standard, the original IEEE and The Open Group Standard
  100. is the referee document. The original Standard can be obtained online at
  101. http://www.opengroup.org/unix/online.html .
  102. .PP
  103. Any typographical or formatting errors that appear
  104. in this page are most likely
  105. to have been introduced during the conversion of the source files to
  106. man page format. To report such errors, see
  107. https://www.kernel.org/doc/man-pages/reporting_bugs.html .