|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
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.
|C.3.1 The common syntax|
|C.3.2 Security and the Trigger Scripts||Trigger script security|
|C.3.3 The commit support files||The commit support files (commitinfo, verifymsg, loginfo)|
|C.3.4 Commitinfo||Pre-commit checking|
|C.3.5 Verifying log messages||How are log messages evaluated?|
|C.3.6 Loginfo||Where should log messages be sent?|
|C.3.7 Logging admin commands|
|C.3.8 Taginfo||Verifying/Logging tags|
|C.3.9 Logging tags|
|C.3.10 Logging watch commands|
|C.3.11 Launch a Script before Proxying||Launch a script on a secondary server prior to becoming a write proxy|
|C.3.12 Launch a Script after Proxying||Launch a script on a secondary server after completing proxy operations|
This document was generated on September, 14 2007 using texi2html 1.76.