In a complete PIKT setup, you have all eight basic configuration files: systems.cfg, defines.cfg, macros.cfg, alerts.cfg, alarms.cfg, objects.cfg, programs.cfg, and files.cfg. You might, in addition, have #include file spinoffs from those basic eight.
It is possible to deploy PIKT in a partial configuration, with subsets of the eight basic config file types. systems.cfg is always required, but all the rest are optional.
For example, here are a few (among many) of the possible PIKT setups:
- piktc as rsh/ssh replacement (no macros or defines): systems.cfg only.
- piktc as rsh/ssh replacement (with macros and possibly defines): systems.cfg, macros.cfg; and optionally defines.cfg.
- piktc as rdist replacement: systems.cfg, files.cfg; and optionally programs.cfg, macros.cfg, defines.cfg.
- a centrally directed cron replacement: systems.cfg, alerts.cfg, alarms.cfg; and optionally macros.cfg, defines.cfg.
- system/network monitor (but without system files management): all config files except files.cfg.
- system/network monitor; rsh/ssh, rdist, cron replacements: all config files.
So, you may utilize all that PIKT has to offer, or just pick and choose among its many functionalities.
|prev page||1st page||next page|