Skip to content

Commit 033587a

Browse files
committed
mount_nullfs.8: document unixbypass and nounixbypass
Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D52983
1 parent 6fa205a commit 033587a

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed

sbin/mount_nullfs/mount_nullfs.8

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,14 +90,40 @@ See the
9090
.Xr mount 8
9191
man page for possible options and their meanings.
9292
Additionally the following option is supported:
93-
.Bl -tag -width nocache
93+
.Bl -tag -width nounixbypass
9494
.It Cm nocache
9595
Disable metadata caching in the null layer.
9696
Some lower-layer file systems may force this option.
9797
Depending on the access pattern,
9898
this may result in increased lock contention.
9999
.It Cm cache
100100
Force enable metadata caching.
101+
.It Cm nounixbypass
102+
Disable bypassing
103+
.Xr unix 4
104+
socket files used for
105+
.Xr bind 2
106+
and
107+
.Xr connect 2 ,
108+
to the lower (mounted-from) filesystem layer.
109+
.Pp
110+
The effect is that lower and upper (bypassed) unix sockets
111+
are separate.
112+
.It Cm unixbypass
113+
Enable the bypass of unix socket file to lower filesystem layer.
114+
This is default.
115+
.Pp
116+
The effect is that
117+
.Xr bind 2
118+
and
119+
.Xr connect 2
120+
operations on a unix socket done from either the upper (nullfs) or lower
121+
layer path are performed on same unix socket.
122+
For instance, if a server
123+
.Xr bind 2
124+
is done on a socket in the lower layer, then
125+
.Xr connect 2
126+
on the socket file accessed via the nullfs mount, connects to the server.
101127
.El
102128
.El
103129
.Pp

0 commit comments

Comments
 (0)