[Bug 258010] kqueue shortcoming for desktop usage
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258010] kqueue shortcoming for desktop usage"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 23 Aug 2021 17:28:58 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258010
Bug ID: 258010
Summary: kqueue shortcoming for desktop usage
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: tcberner@freebsd.org
Moin moin
FreeBSDs file monitoring via kqueue/kevent requires files to be opened to be
monitored.
This has a few draw back which mostly crop up in desktop systems (gnome, kde,
...) that
have support for monitoring and indexing the users home directory.
Issue 1: A big ~ leads to file handle exhaustion
As all files have to be opened the kern.maxfiles sysctl needs to be tuned by
users.
=> desktops won't work out of the box for those users
=> unnecessary crashes happening on startup of desktop sessions
Issue 2: Socket files cannot be monitored
As open() cannot be called on socket files, you cannot monitor a socket file
for its deletion.
Linux's file monitoring seems to be able to support these use cases -- maybe a
re-implementation of their file monitoring should be considered inside FreeBSD.
An other option would probably be to extend kqueue for these use cases.
mfg Tobias
--
You are receiving this mail because:
You are the assignee for the bug.