diff options
-rw-r--r-- | bin/ln/symlink.7 | 3 | ||||
-rw-r--r-- | sbin/mountd/exports.5 | 9 | ||||
-rw-r--r-- | sbin/mountd/netgroup.5 | 18 | ||||
-rw-r--r-- | usr.sbin/mountd/exports.5 | 9 | ||||
-rw-r--r-- | usr.sbin/mountd/netgroup.5 | 18 |
5 files changed, 38 insertions, 19 deletions
diff --git a/bin/ln/symlink.7 b/bin/ln/symlink.7 index 6e6d5a7..83f9973 100644 --- a/bin/ln/symlink.7 +++ b/bin/ln/symlink.7 @@ -132,7 +132,8 @@ The .Bx 4.4 system differs from historical 4BSD systems in that the system call .Xr chown 2 -has been changed to follow symbolic links. The +has been changed to follow symbolic links. +The .Xr lchown 2 system call was added later when the limitations of the new .Xr chown 2 diff --git a/sbin/mountd/exports.5 b/sbin/mountd/exports.5 index 9a148de..6506b5b 100644 --- a/sbin/mountd/exports.5 +++ b/sbin/mountd/exports.5 @@ -163,8 +163,10 @@ in an effort to be backward compatible with older export file formats. exports strictly according to the spec (RFC 2054 and RFC 2055) can be done with the .Fl public -flag. However, this flag in itself allows r/w access to all files in -the filesystem, not requiring reserved ports and not remapping uids. It +flag. +However, this flag in itself allows r/w access to all files in +the filesystem, not requiring reserved ports and not remapping uids. +It is only provided to conform to the spec, and should normally not be used. For a .Tn WebNFS @@ -186,7 +188,8 @@ A option can be used to specify a file whose handle will be returned if a directory is looked up using the public filehandle ( .Tn WebNFS Ns ). -This is to mimic the behavior of URLs. If no +This is to mimic the behavior of URLs. +If no .Fl index option is specified, a directory filehandle will be returned as usual. The diff --git a/sbin/mountd/netgroup.5 b/sbin/mountd/netgroup.5 index db7118c..6451ec6 100644 --- a/sbin/mountd/netgroup.5 +++ b/sbin/mountd/netgroup.5 @@ -67,7 +67,8 @@ Any of the comma separated fields may be empty to specify a ``wildcard'' value or may consist of the string ``-'' to specify ``no valid value''. The members of the list may be separated by whitespace and/or commas; the ``\e'' character may be used at the end of a line to specify -line continuation. Lines are limited to 1024 characters. +line continuation. +Lines are limited to 1024 characters. The functions specified in .Xr getnetgrent 3 should normally be used to access the @@ -82,25 +83,29 @@ are only used in conjunction with .Tn NIS and local .Pa /etc/netgroup -files are ignored. With +files are ignored. +With .Fx , .Nm Ns s can be used with either .Tn NIS or local files, but there are certain -caveats to consider. The existing +caveats to consider. +The existing .Nm system is extremely inefficient where .Fn innetgr 3 lookups are concerned since .Nm -memberships are computed on the fly. By contrast, the +memberships are computed on the fly. +By contrast, the .Tn NIS .Nm database consists of three separate maps (netgroup, netgroup.byuser and netgroup.byhost) that are keyed to allow .Fn innetgr 3 -lookups to be done quickly. The +lookups to be done quickly. +The .Fx .Nm system can interact with the @@ -152,7 +157,8 @@ token, the local data and the netgroup map will be processed as a single combined .Nm -database. While this configuration is the most flexible, it +database. +While this configuration is the most flexible, it is also the least efficient: in particular, .Fn innetgr 3 lookups will be especially slow if the diff --git a/usr.sbin/mountd/exports.5 b/usr.sbin/mountd/exports.5 index 9a148de..6506b5b 100644 --- a/usr.sbin/mountd/exports.5 +++ b/usr.sbin/mountd/exports.5 @@ -163,8 +163,10 @@ in an effort to be backward compatible with older export file formats. exports strictly according to the spec (RFC 2054 and RFC 2055) can be done with the .Fl public -flag. However, this flag in itself allows r/w access to all files in -the filesystem, not requiring reserved ports and not remapping uids. It +flag. +However, this flag in itself allows r/w access to all files in +the filesystem, not requiring reserved ports and not remapping uids. +It is only provided to conform to the spec, and should normally not be used. For a .Tn WebNFS @@ -186,7 +188,8 @@ A option can be used to specify a file whose handle will be returned if a directory is looked up using the public filehandle ( .Tn WebNFS Ns ). -This is to mimic the behavior of URLs. If no +This is to mimic the behavior of URLs. +If no .Fl index option is specified, a directory filehandle will be returned as usual. The diff --git a/usr.sbin/mountd/netgroup.5 b/usr.sbin/mountd/netgroup.5 index db7118c..6451ec6 100644 --- a/usr.sbin/mountd/netgroup.5 +++ b/usr.sbin/mountd/netgroup.5 @@ -67,7 +67,8 @@ Any of the comma separated fields may be empty to specify a ``wildcard'' value or may consist of the string ``-'' to specify ``no valid value''. The members of the list may be separated by whitespace and/or commas; the ``\e'' character may be used at the end of a line to specify -line continuation. Lines are limited to 1024 characters. +line continuation. +Lines are limited to 1024 characters. The functions specified in .Xr getnetgrent 3 should normally be used to access the @@ -82,25 +83,29 @@ are only used in conjunction with .Tn NIS and local .Pa /etc/netgroup -files are ignored. With +files are ignored. +With .Fx , .Nm Ns s can be used with either .Tn NIS or local files, but there are certain -caveats to consider. The existing +caveats to consider. +The existing .Nm system is extremely inefficient where .Fn innetgr 3 lookups are concerned since .Nm -memberships are computed on the fly. By contrast, the +memberships are computed on the fly. +By contrast, the .Tn NIS .Nm database consists of three separate maps (netgroup, netgroup.byuser and netgroup.byhost) that are keyed to allow .Fn innetgr 3 -lookups to be done quickly. The +lookups to be done quickly. +The .Fx .Nm system can interact with the @@ -152,7 +157,8 @@ token, the local data and the netgroup map will be processed as a single combined .Nm -database. While this configuration is the most flexible, it +database. +While this configuration is the most flexible, it is also the least efficient: in particular, .Fn innetgr 3 lookups will be especially slow if the |