The following commit has been merged in the openafs-stable-1_6_x branch:
commit c4752dca439a12c2be162eb98869ef37d7c43767
Author: Stephan Wiesand <[email protected]>
Date: Wed Mar 12 10:47:17 2014 +0100
doc: bos setrestricted -mode 0 does make sense
Commit 070230ab76e1df338db3f2a7971111ca976a0c1a added documentation of
the mode parameter to bos setrestricted, claiming that the value 0 is
useless, and commit eee0bf5871944d919951cc8b7b4908ee909c3b62 added
documentation of the restrictmode entry in BosConfig, claiming that it
can only be set back to 0 with an editor. Both claims are wrong, since
bos setrestricted -mode 0 will do exactly that (if it succeeds, which
it only can if the server is running in unrestricted mode, which can
be achieved by sending it the FPE signal). Fix the man pages
accordingly.
Reviewed-on: http://gerrit.openafs.org/10885
Tested-by: BuildBot <[email protected]>
Reviewed-by: Benjamin Kaduk <[email protected]>
Reviewed-by: Marc Dionne <[email protected]>
Reviewed-by: Andrew Deason <[email protected]>
Reviewed-by: Michael Meffie <[email protected]>
Reviewed-by: D Brashear <[email protected]>
(cherry picked from commit da549eea21941681c075796512a27a830259c835)
Change-Id: Iea8f252829ba6192176da0ceba464cbc41aad53c
Reviewed-on: http://gerrit.openafs.org/10955
Reviewed-by: Andrew Deason <[email protected]>
Tested-by: Stephan Wiesand <[email protected]>
Reviewed-by: Stephan Wiesand <[email protected]>
doc/man-pages/pod5/BosConfig.pod | 2 --
doc/man-pages/pod8/bos_setrestricted.pod | 16 ++++++++--------
2 files changed, 8 insertions(+), 10 deletions(-)
--
OpenAFS Master Repository
_______________________________________________
OpenAFS-cvs mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-cvs
