I am writing a script that will dynamically create a monit rc
configuration file. This script will recursively walk a relatively
deep and entangled nest of directories and collect information
about all of the resources it finds in those directories ( e.g.,
files, symbolic links, subdirectories). It will then create an
entry in the monit rc file for each resource it finds.
A preliminary walk of the tree reports to me that it has discovered
a whopping 277,924 resource files. I anticipate that the
corresponding monit configuration file will total in the tens of
megabytes in size once it is created by this script. This is a
security requirement and I need to know if anything changes state
in this deep and entangled section of my file system (I expect it
to be static almost always).
I will be running an instance of a monit daemon to monitor these
file system resources with this very large monit configuration file
that is dynamically generated by my script. It will run on a cycle
of once per day (so the daemon will then go into sleep mode most of
the day).
I am wondering if anyone has ever used monit to monitor hundreds of
thousands of file system resources? I am also wondering how monit
will handle such a large configuration file? Does the monit daemon
parse the configuration file once and then load it into memory
(even if the monit daemon sleeps most of the time, is the
configuration file cached in RAM)? If so, then I might be in
trouble since I only have 1 GB of RAM on my server.
Thank you for any insights!
Cheers,
Sergio