[Bug 192562] zfs(5): missing manpage

2024-05-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192562

Alexander Ziaee  changed:

   What|Removed |Added

 CC||concussious.bugzilla@runbox
   ||.com

--- Comment #5 from Alexander Ziaee  ---
Update: We are moving all the filesystem manuals to section four in
https://github.com/freebsd/freebsd-src/pull/1077
feedback and suggestions are desired in that thread :)

Filesystem pages in section five don't describe file formats, they describe the
kernel interface of the filesystem driver.

ZFS is actually demonstrating what we're trying to do: there's zfs(4) for that,
and then z$whatever(8) for the tooling and z$whatever(7) for concept overviews.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 278947] front-end proxy varnish returns truncated HTML pages

2024-05-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278947

Li-Wen Hsu  changed:

   What|Removed |Added

 CC||lw...@freebsd.org
   Assignee|d...@freebsd.org |cluster...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 130238] nfs.lockd man page doesn't mention NFSLOCKD option or nfslockd module

2024-05-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=130238

Dag-Erling Smørgrav  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED
  Flags|mfc-stable14?,  |mfc-stable14+,
   |mfc-stable13?   |mfc-stable13+

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 130238] nfs.lockd man page doesn't mention NFSLOCKD option or nfslockd module

2024-05-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=130238

--- Comment #7 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=7f97e3f47149ee44b06e3877f1bab1834c6a9307

commit 7f97e3f47149ee44b06e3877f1bab1834c6a9307
Author: Dag-Erling Smørgrav 
AuthorDate: 2024-05-10 09:23:13 +
Commit: Dag-Erling Smørgrav 
CommitDate: 2024-05-14 06:59:12 +

Add man page for nfslockd.

PR: 130238
MFC after:  3 days
Differential Revision:  https://reviews.freebsd.org/D45139

(cherry picked from commit 44e72c6e2e6bcfa2cba89afb92fa05f6ac4d5660)

 share/man/man4/Makefile |  1 +
 share/man/man4/nfslockd.4 (new) | 45 +
 usr.sbin/rpc.lockd/lockd.c  |  3 ++-
 usr.sbin/rpc.lockd/rpc.lockd.8  |  5 +++--
 4 files changed, 51 insertions(+), 3 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 130238] nfs.lockd man page doesn't mention NFSLOCKD option or nfslockd module

2024-05-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=130238

--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=cd7dc8deefbce5dc3b5aaab611bbee7af6eccf62

commit cd7dc8deefbce5dc3b5aaab611bbee7af6eccf62
Author: Dag-Erling Smørgrav 
AuthorDate: 2024-05-10 09:23:13 +
Commit: Dag-Erling Smørgrav 
CommitDate: 2024-05-14 06:58:40 +

Add man page for nfslockd.

PR: 130238
MFC after:  3 days
Differential Revision:  https://reviews.freebsd.org/D45139

(cherry picked from commit 44e72c6e2e6bcfa2cba89afb92fa05f6ac4d5660)

 share/man/man4/Makefile |  1 +
 share/man/man4/nfslockd.4 (new) | 45 +
 usr.sbin/rpc.lockd/lockd.c  |  3 ++-
 usr.sbin/rpc.lockd/rpc.lockd.8  |  5 +++--
 4 files changed, 51 insertions(+), 3 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 262895] access(2) man page should mention softlinks

2024-05-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262895

Dag-Erling Smørgrav  changed:

   What|Removed |Added

 CC||d...@freebsd.org

--- Comment #4 from Dag-Erling Smørgrav  ---
Jamie, how exactly did you “almost get bitten” by this?  `access()` etc always
dereference the symbolic link because the question they answer is “what would
happen if I tried to `open()` this path” and `open()` always dereferences
symbolic links.  Furthermore, as is already noted in the manual page, you
should probably not be using `access()` at all for reasons entirely unrelated
to whether or not it follows symbolic links.

-- 
You are receiving this mail because:
You are on the CC list for the bug.