Troubleshooting instructions say to disable kqueue… Google-fu did not produce any useful results.
How do I disable kqueue directory watching?
You need to provide a lot more context than this. Why do you think you need to disable kqueue?
To further elucidate: kqueue is the kernel event notification system in FreeBSD (TrueNAS Core). It cannot be disabled.
Some applications may use kqueue for various purposes and some usage of that may be enabled / disabled, but that is very application-specific, and so your question cannot be answered without further information.
1 Like
Troubleshooting very old minidlna inside a jail. Old comments regarding crashes say it works with kqueue disabled.
So the way you’d go about this is look up what the configuration files are for minidlna, then look up their manpages to see whether there’s an option to disable kqueue. Typically this sort of application would use kqueue to monitor for changes to files, if you disable kqueue integration (typically through a libinotify shim – parameter may be related to inotify) then you will need to ensure the application periodically scans its directories for changes because the kernel will no longer provide change notifications.
1 Like
Oh thanks for the tip. Turns out I had to recompile it without the kqueue patch… Kind of a shame that it has to now rescan on a timer, I notice it’s very CPU intensive on this box…
Would have been nice if there wasn’t a bug in the kqueue patch in the port…
There are some design differences between kqueue (BSD) and epoll (Linux) that developers don’t realize and think they can substitute one for the other. This is aggravated in that libinotify layers over the top of them. Common usage patterns like “watch every file in this huge directory tree for changes” can quickly cause exhaustion of open files and server crash when using libinotify on FreeBSD. If you really need this feature I’d say you should probably consider upgrading to SCALE at some point.