Sign In Sign Out Mailing Lists Unsubscribe or Change Settings Help

bugzilla.org

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
configset  GLOBAL  triggers <<TAG
[VALUE LINES]
TAG
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
configset listname triggers <<TAG
[VALUE LINES]
TAG
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Default Value : checksum | daily ... (only first item is shown)
Data Type     : triggers
Category      : miscellany
Password Notes: Visible only with password. Set with global password. 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

EXAMPLE:
configset GLOBAL triggers <<ENDGLOBAL
checksum | 3rd(17),10th(9),17th(11),24th(19)
delay    | hourly
inactive | daily
log      | weekly
session  | monday(6,12,18), thursday(8)
token    | always  
ENDGLOBAL

configset ANOTHER_LIST triggers <<ENDLIST
bounce   | daily
checksum | 3rd(17),10th(9),17th(11),24th(19)
delay    | hourly
inactive | daily
post     | thursday
vacation | hourly
ENDLIST

Triggers are actions that occur periodically, as often as once per hour.
They are used to remove expired data and complete delayed requests.

Each trigger consists of a name and a set of times during which the
trigger is issued.  The name and times are separated by vertical bars
('|') or colons, as in:
  session  | monday(6,12,18), thursday(8)

See "help times" for a description of the times syntax.

When the software was installed, a cron job should have been set up to
call the mj_trigger program on an hourly basis.  During the hourly
cron job, the times for each trigger in the triggers setting are
compared to the current day and time.  Triggers whose times match
the current time are executed by the mj_trigger program.

The following actions can be triggered via the GLOBAL pseudo-list:
 checksum - Expire posted message checksums and message-id data.
 delay    - Complete delayed requests.
 inactive - Remove inactive registered addresses with no subscriptions.
 log      - Expire entries from the main log.
 session  - Expire old session data.
 token    - Issue reminders and remove expired tokens and temporary passwords.

The following actions can be triggered via regular mailing lists:
 bounce   - Expire delivery failure information which is outdated.
 checksum - Expire posted message checksums and message-id data.
 delay    - Complete delayed requests and post delayed messages.
 inactive - Remove inactive subscriptions that are on vacation indefinitely.
 post     - Expire data from the "post_limits" database.
 vacation - Restore delivery for people whose vacation has elapsed.

A value for each action in the "triggers" setting is recommended.
Triggers that are not listed explicitly will be run daily.

The times field follows the standard Majordomo syntax (see "help times").
"always" and "hourly" are identical:  the specified trigger is always run.  
"never" skips the specified trigger.

In addition to the named triggers, commands in files in the private
file space of a list can be run.  The file name must start with
a solidus, /.  The file must not reside in the public or help directory.
The commands in the file will undergo variable substitution using
the standard substitutions before they are run (see "help variables" for
more details).  For example, within a file, the commands:

  default user $OWNER
  lists-full $LIST

would contain the actual list owners' address and list name when the
commands are run.  The file should always begin with a "default user"
command; otherwise, the results will not be mailed.  See "help default"
for more information.  See "help admin_documents" for an introduction
to the file space and document management.

The triggers configuration setting has no influence upon the times that
digests are triggered.  See "help configset_digests" for more
information about the delivery of message digests.

It is possible to use comments before, between, and after the individual
triggers.  Comments are lines that begin with a '#'.  You can use 
comments as a reminder of what a trigger does or why it was chosen, 
but comments have no impact on how the triggers work.


See Also:
   help admin
   help admin_documents
   help configset_access_rules
   help configset_digests
   help configset_dup_lifetime
   help configset_inactive_lifetime
   help configset_latchkey_lifetime
   help configset_log_lifetime
   help configset_post_lifetime
   help configset_post_limits
   help configset_session_lifetime
   help configset_token_lifetime
   help default
   help mj_trigger
   help times

This is the "configset_triggers" help document for 
Majordomo 2, version 0.1201103110.

For a list of all help documents, send the following command:
   help topics
in the body of a message to majordomo@bugzilla.org.

If you need assistance, please contact the bugzilla.org administrators.
Sign In Sign Out Mailing Lists Unsubscribe or Change Settings Help