Date: Fri, 23 Feb 2024 12:41:09 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 277238] kqueue(2), kevent(2) manpages are confusing and/or underspecified Message-ID: <bug-277238-227-S43K60TTZI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277238-227@https.bugs.freebsd.org/bugzilla/> References: <bug-277238-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277238 unitrunker <unitrunker@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |unitrunker@gmail.com --- Comment #1 from unitrunker <unitrunker@gmail.com> --- As I see it, the way forward is to break this up into smaller pieces and su= bmit a patch for each one. I suspect each type likely deserves a separate document - which can be link= ed from the main kqueue / kevent mandoc page. Attaching bits of sample code illustrating observed behavior is extemely helpful to the review process. Along these lines, I'd like to add my two cents on documenting how to watch files and directories (VNODEs). For example, the read and write events on a directory don't tell you what changed, only that - in the case of a write - something changed. The best I can determine is you need to take a snapshot = of the directory and, upon receiving a write event, re-read the directory and compare to see what changed. It would be nice if the read and write events gave us some sort of identity= as a clue to what changed. Maybe place the top inode of the directory entry th= an changed into the ext[] data, for example. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277238-227-S43K60TTZI>