piktx

piktx is the PIKT remote command execution utility.  It takes the following command-line arguments:

Usage:  piktx <-xXvhGV>
              [-p#]
               +C            <command(s)>
               +|-H      all|<host(s)>

        -x                         execute alert(s)/script(s)
        -X                         execute alert(s)/script(s) with no wait
        -v                         run in verbose mode
        -h                         show program help
        -G                         run in debug mode
        -V                         show version info
        -p#                        pause # seconds
        +C            <command(s)> include command string(s)
        +|-H      all|<host(s)>    include/exclude
                                   host(s)/os(es)/group(s)/
                                     alias(es)

Why use piktx instead of piktc for remote command execution?  For the following reasons:

• piktc runs on the master system only (for most operations, including remote command execution).  piktx will run on any PIKT system, master or slave.
• piktc does not allow multiple, concurrent program runs (except for some auxiliary operations, for example 'piktc -L' or 'piktc -M').  With piktx, more than one simultaneous run is possible.  (With piktc, if one sysadmin has launched a piktc operation, this effectively blocks other sysadmins from doing the same.  With piktx, there is no blocking.)
• piktx uses ssh (or, if you prefer, rsh; to enable this, you need to hand-edit the piktx code) to handle the actual remote command execution.  piktc uses the piktc-to-piktc_svc network transport.

In order for piktx to be useful on slave systems, you must install a limited set of .cfg files in the cfgdir on those systems.  Typically, these files would include just systems.cfg (and perhaps a systems subdirectory), macros.cfg (and perhaps a macros subdirectory), and maybe defines.cfg (and perhaps a defines subdirectory).  See the sample files.cfg for how to set this up.  You would install the .cfg files to the slave systems with the usual 'piktc -iv +F all +H ...'.  In your files.cfg setup, be sure to place a '#if ! piktmaster ... #endif' wrapper around the installable .cfg files so as not to inadvertently clobber your master's .cfg files!

See piktc for a fuller explanation of each piktx command option.

Unlike many of the other PIKT binaries (which are written using a combination of C, lex, and yacc), piktx (like piktf, pikth & rkey) is written in Perl.

prev page

1st page

next page