Partial Configurations

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.
Other combinations are possible, but these are the most common.

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
 
Home | FAQ | News | Intro | Samples | Tutorial | Reference | Software
Developer's Notes | Licensing | Authors | Pikt-Users | Pikt-Workers | Related Projects | Site Index | Privacy Policy | Contact Us
Page best viewed at 1024x768 or greater.   Page last updated 2019-01-12.   This site is PIKT® powered.
Copyright © 1998-2019 Robert Osterlund. All rights reserved.
Home FAQ News Intro Samples Tutorial Reference Software
PIKT Logo
PIKT Page Title
View sample
script scheduling
macros