objects.cfg #include files

objects.cfg specifies system objects to be monitored, often with associated data.

The top-level objects.cfg typically references #include files, each with a single category of things to be monitored, for example:

dirs_system_objects.cfg (system directory lists)
- dirs_system_redhat_linux_objects.cfg (Red Hat Linux system directories)
- dirs_system_suse_linux_objects.cfg (SuSE Linux system directories)
- and so on for other operating systems...
files_system_objects.cfg (system file lists)
- files_system_redhat_linux_objects.cfg (Red Hat Linux system files)
- files_system_suse_linux_objects.cfg (SuSE Linux system files)
- files_system_solaris_objects.cfg (Solaris system files)
- and so on for other operating systems...
security_objects.cfg (file checksums)
- checksums_redhat_linux_objects.cfg (Red Hat Linux checksums)
- checksums_suse_linux_objects.cfg (SuSE Linux checksums)
- and so on for other operating systems...

per_user_process_counts_objects.cfg (per-user process count limits)
process_times_objects.cfg (process time limits)
dirs_filestat_objects.cfg (directory attributes)
diskcaps_objects.cfg (disk capacity limits)
fileages_objects.cfg (file modification times)
files_unwanted_objects.cfg (unwanted files)
logs_system_objects.cfg (system log files)
process_system_local_objects.cfg (local system processes)
dirs_user_objects.cfg (user directories)
http_status_codes_objects.cfg (http status codes)
and so on for other object #include files...

(A note about page layout: In the interest of readability, we have added artificial line wraps in many examples. Even though displayed here broken up across several screen lines, in general quoted strings, preprocessor directives, macro definitions, .log & .conf entries, and so on should all be unbroken on a single line.)

See also the Introduction and Developer's Notes pages for additional samples (with commentary).