(cvs.info.gz) Trigger Scripts

(cvs.info.gz) Administrative files

 
 C.3 The Trigger Scripts
 =======================
 
 Several of the administrative files support triggers, or the launching
 external scripts or programs at specific times before or after
 particular events, during the execution of CVS commands.  These hooks
 can be used to prevent certain actions, log them, and/or maintain
 anything else you deem practical.
 
    All the trigger scripts are launched in a copy of the user sandbox
 being committed, on the server, in client-server mode.  In local mode,
 the scripts are actually launched directly from the user sandbox
 directory being committed.  For most intents and purposes, the same
 scripts can be run in both locations without alteration.

 
* syntax                      The common syntax
* Trigger Script Security     Trigger script security
 
* commit files                The commit support files (commitinfo,
                                 verifymsg, loginfo)
*   commitinfo                Pre-commit checking
*   verifymsg                 How are log messages evaluated?
*   loginfo                   Where should log messages be sent?
 
* postadmin                   Logging admin commands
* taginfo                     Verifying/Logging tags
* posttag                     Logging tags
* postwatch                   Logging watch commands
 
* preproxy                    Launch a script on a secondary server prior
 				to becoming a write proxy
* postproxy                   Launch a script on a secondary server after
 				completing proxy operations

Info Catalog

(cvs.info.gz) Wrappers

(cvs.info.gz) Administrative files

(cvs.info.gz) rcsinfo

automatically generated byinfo2html

(cvs.info.gz) Trigger Scripts

Menu