|
Although you can assign PIKT to a wide variety of tasks, PIKT is used primarily for system monitoring, and secondarily for configuration management. For sample problem reports, go here. Following are some sample configurations:
-
systems.cfg is where you specify host systems, aliases, and groups. The top-level systems.cfg file might reference smaller #include files, some of them perhaps auto-generated (examples not shown).
-
defines.cfg specifies a set of "defines"--preprocessor logical switches for including or excluding sections of the configuration files. The top-level defines.cfg might reference #include files, for example:
-
macros.cfg specifies a collection of macros, or preprocessor text substitutions. The top-level macros.cfg might reference #include files.
-
alerts.cfg groups together alarm and other program scripts and schedules them for execution. The top-level alerts.cfg might, but typically does not, reference #include files (examples not shown).
-
alarms.cfg is a series of one or more Pikt scripts or alarm definitions. The top-level alarms.cfg might reference #include files.
|
-
objects.cfg specifies system objects to be monitored, often with associated data. The top-level objects.cfg typically references #include files.
-
programs.cfg contains support scripts written in other script languages (other than the Pikt language). The top-level programs.cfg typically references #include files. each with a single program script.
-
files.cfg specifies system configuration files, and indeed any text file. The top-level files.cfg typically references #include files, each with a single configuration file.
-
piktc commands shows some typical operations of the PIKT preprocessor.
-
PIKT.conf is the PIKT master configuration file.
-
piktd.conf shows some typical alert schedules.
-
keys.conf is the encryption keys file.
|
|
(A note about page layout: In the interest of readability, we have added artificial line wraps in several examples. Even though displayed here broken up across several screen lines, in general quoted strings, preprocessor directives, etc. should all be unbroken on a single line.)
These samples do not constitute a complete, coherent PIKT configuration, nor are they necessarily current. Much has been left out. The provided examples are suggestive only. Use them as inspiration for designing and writing your own configuration.
It should be emphasized that the examples shown here are not an intrinsic part of PIKT. You may adopt the suggested formats, layouts, #include files, macros, alert schedules, alarm scripts, object sets, etc., or you may devise a completely different setup. You may use the Pikt script language, or employ the one you favor (such as Perl, Python, or whatever). You may utilize PIKT for everything--for system monitoring, reporting and fixing problems, configuration management, systems security, document formatting, job scheduling, file installation, etc.--or just pick and choose among its many functionalities. Be as complicated as you like, or keep things simple. You have the utmost flexibility. The choices are entirely yours.
See also the Developer's Notes pages for additional samples (with commentary).
Home |
FAQ |
News |
Intro |
Samples |
Tutorial |
Reference |
Software |
Authors |
Licensing |
SiteSearch
Links |
SiteIndex |
Pikt-Users |
Pikt-Workers |
Contribute |
ContactUs |
Top of Page
Page best viewed at 1024x768.
Page last updated 2005-06-22.
This site is
PIKT®
powered.
PIKT® is a registered trademark of the University of Chicago.
Copyright © 1998-2005 Robert Osterlund. All rights reserved.
|
|
|