Real time indexing: miscellaneous details

By default, the messages from the indexing daemon will be sent to the same file as those from the interactive commands (logfilename). You may want to change this by setting the daemlogfilename and daemloglevel configuration parameters. Also the log file will only be truncated when the daemon starts. If the daemon runs permanently, the log file may grow quite big, depending on the log level.

Increasing resources for inotify. On Linux systems, monitoring a big tree may need increasing the resources available to inotify, which are normally defined in /etc/sysctl.conf.

          ### inotify
          #
          # cat  /proc/sys/fs/inotify/max_queued_events   - 16384
          # cat  /proc/sys/fs/inotify/max_user_instances  - 128
          # cat  /proc/sys/fs/inotify/max_user_watches    - 16384
          #
          # -- Change to:
          #
          fs.inotify.max_queued_events=32768
          fs.inotify.max_user_instances=256
          fs.inotify.max_user_watches=32768
        

Especially, you will need to trim your tree or adjust the max_user_watches value if indexing exits with a message about errno ENOSPC (28) from inotify_add_watch.

Slowing down the reindexing rate for fast changing files. When using the real time monitor, it may happen that some files need to be indexed, but change so often that they impose an excessive load for the system. Recoll provides a configuration option to specify the minimum time before which a file, specified by a wildcard pattern, cannot be reindexed. See the mondelaypatterns parameter in the configuration section.