diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2010-10-12 06:45:38 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2010-10-12 06:49:17 +0200 |
| commit | 008f1ecc4351f2874f14cc5d1b75fae73ed82f17 (patch) | |
| tree | ad0553833645320cc53764ca76db212ca242ff33 /man7/unix.7 | |
| parent | 1f409d5d0be79dbd4919b117035a1d91f1c30a3b (diff) | |
| download | man-pages-008f1ecc4351f2874f14cc5d1b75fae73ed82f17.tar.gz | |
intro.1, time.1, accept.2, bind.2, connect.2, execve.2, flock.2, getdents.2, getpriority.2, getuid.2, intro.2, ioctl.2, mincore.2, mknod.2, personality.2, ptrace.2, read.2, recv.2, select_tut.2, send.2, sendfile.2, shmctl.2, sigaction.2, signal.2, stat.2, times.2, truncate.2, umask.2, wait.2, MB_CUR_MAX.3, MB_LEN_MAX.3, argz_add.3, btowc.3, clearenv.3, clock.3, cmsg.3, end.3, endian.3, errno.3, exit.3, fgetwc.3, fgetws.3, fopen.3, fputwc.3, fputws.3, fseek.3, fwide.3, getfsent.3, getgrnam.3, gethostid.3, getipnodebyname.3, getmntent.3, getpwnam.3, getwchar.3, grantpt.3, iconv.3, iconv_close.3, iconv_open.3, insque.3, intro.3, iswalnum.3, iswalpha.3, iswblank.3, iswcntrl.3, iswctype.3, iswdigit.3, iswgraph.3, iswlower.3, iswprint.3, iswpunct.3, iswspace.3, iswupper.3, iswxdigit.3, malloc.3, mblen.3, mbrlen.3, mbrtowc.3, mbsinit.3, mbsnrtowcs.3, mbsrtowcs.3, mbstowcs.3, mbtowc.3, mkstemp.3, mktemp.3, nl_langinfo.3, openpty.3, posix_openpt.3, printf.3, ptsname.3, putwchar.3, qecvt.3, rcmd.3, readdir.3, rexec.3, rpc.3, setnetgrent.3, shm_open.3, sigpause.3, stdin.3, stpcpy.3, strftime.3, strptime.3, syslog.3, towctrans.3, towlower.3, towupper.3, ttyslot.3, ungetwc.3, unlocked_stdio.3, wcpcpy.3, wcpncpy.3, wcrtomb.3, wcscasecmp.3, wcscat.3, wcschr.3, wcscmp.3, wcscpy.3, wcscspn.3, wcsdup.3, wcslen.3, wcsncasecmp.3, wcsncat.3, wcsncmp.3, wcsncpy.3, wcsnlen.3, wcsnrtombs.3, wcspbrk.3, wcsrchr.3, wcsrtombs.3, wcsspn.3, wcsstr.3, wcstok.3, wcstombs.3, wcswidth.3, wctob.3, wctomb.3, wctrans.3, wctype.3, wcwidth.3, wmemchr.3, wmemcmp.3, wmemcpy.3, wmemmove.3, wmemset.3, wprintf.3, console_ioctl.4, pts.4, elf.5, filesystems.5, hosts.5, proc.5, ttytype.5, boot.7, capabilities.7, credentials.7, epoll.7, glob.7, koi8-r.7, path_resolution.7, pty.7, signal.7, suffixes.7, time.7, unicode.7, unix.7, uri.7, utf-8.7: global fix: s/Unix/UNIX/
The man pages were rather inconsistent in the use of "Unix"
versus "UNIX". Let's go with the trademark usage.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7/unix.7')
| -rw-r--r-- | man7/unix.7 | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/man7/unix.7 b/man7/unix.7 index 3ee333d61b..79effbe8d7 100644 --- a/man7/unix.7 +++ b/man7/unix.7 @@ -31,7 +31,7 @@ The .BR AF_LOCAL ) socket family is used to communicate between processes on the same machine efficiently. -Traditionally, Unix sockets can be either unnamed, +Traditionally, UNIX sockets can be either unnamed, or bound to a file system pathname (marked as being of type socket). Linux also supports an abstract namespace which is independent of the file system. @@ -41,17 +41,17 @@ Valid types are: for a stream-oriented socket and .BR SOCK_DGRAM , for a datagram-oriented socket that preserves message boundaries -(as on most Unix implementations, Unix domain datagram +(as on most UNIX implementations, UNIX domain datagram sockets are always reliable and don't reorder datagrams); and (since Linux 2.6.4) .BR SOCK_SEQPACKET , for a connection-oriented socket that preserves message boundaries and delivers messages in the order that they were sent. -Unix sockets support passing file descriptors or process credentials +UNIX sockets support passing file descriptors or process credentials to other processes using ancillary data. .SS Address Format -A Unix domain socket address is represented in the following structure: +A UNIX domain socket address is represented in the following structure: .in +4n .nf @@ -71,7 +71,7 @@ always contains Three types of address are distinguished in this structure: .IP * 3 .IR pathname : -a Unix domain socket can be bound to a null-terminated file +a UNIX domain socket can be bound to a null-terminated file system pathname using .BR bind (2). When the address of the socket is returned by @@ -169,9 +169,9 @@ followed by 5 bytes in the character set (Thus, there is a limit of 2^20 autobind addresses.) .SS Sockets API The following paragraphs describe domain-specific details and -unsupported features of the sockets API for Unix domain sockets on Linux. +unsupported features of the sockets API for UNIX domain sockets on Linux. -Unix domain sockets do not support the transmission of +UNIX domain sockets do not support the transmission of out-of-band data (the .B MSG_OOB flag for @@ -182,7 +182,7 @@ and The .BR send (2) .B MSG_MORE -flag is not supported by Unix domain sockets. +flag is not supported by UNIX domain sockets. The use of .B MSG_TRUNC @@ -190,11 +190,11 @@ in the .I flags argument of .BR recv (2) -is not supported by Unix domain sockets. +is not supported by UNIX domain sockets. The .B SO_SNDBUF -socket option does have an effect for Unix domain sockets, but the +socket option does have an effect for UNIX domain sockets, but the .B SO_RCVBUF option does not. For datagram sockets, the @@ -233,7 +233,7 @@ The passed file descriptors behave as though they have been created with .BR dup (2). .TP .B SCM_CREDENTIALS -Send or receive Unix credentials. +Send or receive UNIX credentials. This can be used for authentication. The credentials are passed as a .I struct ucred @@ -398,7 +398,7 @@ Creation of a new socket will fail if the process does not have write and search (execute) permission on the directory the socket is created in. Connecting to the socket object requires read/write permission. This behavior differs from many BSD-derived systems which -ignore permissions for Unix sockets. +ignore permissions for UNIX sockets. Portable programs should not rely on this feature for security. @@ -406,7 +406,7 @@ Binding to a socket with a filename creates a socket in the file system that must be deleted by the caller when it is no longer needed (using .BR unlink (2)). -The usual Unix close-behind semantics apply; the socket can be unlinked +The usual UNIX close-behind semantics apply; the socket can be unlinked at any time and will be finally removed from the file system when the last reference to it is closed. @@ -419,7 +419,7 @@ or .BR recvmsg (2) call. -Unix domain stream sockets do not support the notion of out-of-band data. +UNIX domain stream sockets do not support the notion of out-of-band data. .SH EXAMPLE See .BR bind (2). |
