Despite heavy usage of the "Exclude folders and files" options the file integrity plugin continually exhausts inotify resources (even when max watches are set unreasonably high). The problem seems to be that excluding a directory using the --exclude flag of inotifywait while also using the recursive option only prevents events from being raised by the files matching the regex but folders under the directory still consume inotify watch resources. Some experimentation seems to indicate that a possible solution involves using the @<file>" syntax for excluding directories from inotifywait. Folders excluded with @<file> dont seem to be recursed into when setting up watches. My suggestion would be to use the @<file> syntax for setting up the top level folder exclusions, while continuing to use the --exclude flag for the "Custom folders" and "Custom files" options.
Despite heavy usage of the "Exclude folders and files" options the file integrity plugin continually exhausts inotify resources (even when max watches are set unreasonably high). The problem seems to be that excluding a directory using the --exclude flag of inotifywait while also using the recursive option only prevents events from being raised by the files matching the regex but folders under the directory still consume inotify watch resources. Some experimentation seems to indicate that a possible solution involves using the @<file>" syntax for excluding directories from inotifywait. Folders excluded with @<file> dont seem to be recursed into when setting up watches. My suggestion would be to use the @<file> syntax for setting up the top level folder exclusions, while continuing to use the --exclude flag for the "Custom folders" and "Custom files" options.