Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ: Filesystem monitoring failure error message. #286

Merged
merged 1 commit into from Jul 1, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions en/faqgeneral.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,3 +114,9 @@ A: After consulting [JabRef's help](https://docs.jabref.org) and checking whethe

A: See [How to improve the help page](faqcontributing/how-to-improve-the-help-page.md).

## Q: "Unable to monitor file changes. Please close files and processes and restart. You may encounter errors if you continue with this session."

A: This error message has been observed on systems that use [inotify](https://www.man7.org/linux/man-pages//man7/inotify.7.html).
System calls to `inotify_init` and `inotify_add_watch` set `errno` to `EMFILE` when `inotify` has reached its limit. The most
common reason is that `inotify` is running too many instances. To solve this problem, contact you system administrator and request
that they increase the limits defined in `/proc/sys/fs/inotify/max_user_*` files.