Date: Mon, 05 Jun 2023 07:21:21 +0000 From: bugzilla-noreply@freebsd.org To: desktop@FreeBSD.org Subject: [Bug 258010] kqueue shortcoming for desktop usage Message-ID: <bug-258010-39348-VhNN2yFICq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258010-39348@https.bugs.freebsd.org/bugzilla/> References: <bug-258010-39348@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=3D258010 Mark C <fbsd@peralex.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbsd@peralex.com --- Comment #4 from Mark C <fbsd@peralex.com> --- This is an issue that I've been struggling with lately too, also with syncthing. The kqueue workaround works for smaller directory trees, but is unworkable for large collections of files. The number of file descriptors = can be increased, but with millions of files to watch, the system quickly becom= es unusable. There was at least one previous attempt to add inotify-type functionality to FreeBSD in a GSoC project, but I don't know what happened with that: https://www.freebsd.org/status/report-2010-04-2010-06.html#File-System-Chan= ges-Notification A long-running discussion on the forums of the differences between inotify (Linux), fsevents (Mac), and kqueue is here: https://forums.freebsd.org/threads/inotify-for-freebsd.38162/page-3 I also wonder if something could be implemented based on the existing audit framework, which seems to allow file alterations to be watched, although it doesn't have an easy API to use from code. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258010-39348-VhNN2yFICq>