From b2bbcdb6acfbed1a23a1f314ccc1f766996e8946 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Mon, 20 Jun 2016 11:10:35 +0200 Subject: [PATCH] unix.7: Minor wording fixes Signed-off-by: Michael Kerrisk --- man7/unix.7 | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/man7/unix.7 b/man7/unix.7 index b0483b67c..c4f8a8545 100644 --- a/man7/unix.7 +++ b/man7/unix.7 @@ -523,10 +523,10 @@ call. UNIX domain stream sockets do not support the notion of out-of-band data. .\" .SS Socket ownership and permissions -In the Linux implementation, sockets which are visible in the -filesystem honor the permissions of the directory they are in. +In the Linux implementation, +pathname sockets honor the permissions of the directory they are in. 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. +search (execute) permission on the directory in which the socket is created. On Linux, connecting to a stream socket object requires write permission on that socket; @@ -544,13 +544,11 @@ The socket file has all permissions enabled, other than those that are turned off by the process .BR umask (2). -For a socket that is visible in the filesystem, -the owner, group, and permissions can be changed (using +The owner, group, and permissions of a pathname socket can be changed (using .BR chown (2) and .BR chmod (2)). .\" However, fchown() and fchmod() do not seem to have an effect - .\" .SH BUGS When binding a socket to an address,