OpenBSD Mailing List Server

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
configset  GLOBAL  debug = [VALUE]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
configset listname debug = [VALUE]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Default Value : 0
Data Type     : integer
Category      : miscellany
Password Notes: Set with global password. 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

EXAMPLE:
configset GLOBAL debug = 500


The debug setting controls how much debugging information is saved when
an e-mail message is processed.  The value can vary from 0 (no
information is saved) to 1000 (a large amount of information is saved,
including complete traces of SMTP conversations between Majordomo and
your system's mail delivery software (MTA)).

The debug value affects the mail aliases for a list, as determined by
the aliases configuration setting.  Therefore, if the debug value is
changed, the createlist-regen command should be run to regenerate the
aliases.

The debug value is used by the e-mail processing programs (mj_email,
mj_enqueue, mj_queuerun) for all e-mail messages.  It is also used by
the WWW programs (mj_confirm, mj_wwwadm, mj_wwwusr).  The debug value
has no effect upon the other programs.  See the "default debug" section
of "help default" to learn how to change the debug level for the
mj_shell program.

The GLOBAL debug value affects messages that are sent to the Majordomo
server address, majordomo@openbsd.org.

List-specific debug values affect messages that are posted to a mailing
list or sent to the other list-specific addresses, such as the "owner"
alias or the "request" alias.

Debugging information will be stored in several files in the GLOBAL
temporary directory.  This directory is controlled by the GLOBAL tmpdir
configuration setting.  Debugging information for e-mail messages is
stored in the following files:

  mj_email.debug    
  mj_enqueue.debug
  mj_majord.debug
  mj_queuerun.debug
  mj_queueserv.debug
  mj_request.debug
  mj_resend.debug

The other interfaces also have debugging logs in the same directory:

  mj_confirm.debug
  mj_trigger.debug
  mj_wwwadm.debug
  mj_wwwusr.debug

We recommend that the log files be rotated periodically to conserve disk
space.  The following unix shell commands offer one way to do that:
   cp FILE FILE.old
   cp /dev/null FILE

(Substitute the name of an actual log file for FILE.)
Majordomo has no built-in ability to rotate the logs.

Functions that are called very often and have very simple code or
predictable results are logged at a very high level so as to not
pollute the logging results. Generally, debug info is logged in
the following ranges:
   1   -  25: Emergencies anywhere.
   26  -  50: Important External interface functions
   51  - 100: Important core Majordomo functions
   101 - 150: Unimportant interface functions
   150 - 200: Unimportant core functions


                      Note to Majordomo developers

Consider just removing logging from anything you want to
put at a lower level, at least for production.  In fact, for production
we should probably make a script to comment out really low logging info.
   150 - Config file loading + saving
   155 - Config-file sub-saving
   160 - Config file sub-loading
   170 - Config defaulting
   180 - Config::get and upstream callers
   200 - Majordomo::list_legal_name


See Also:
   help admin_domain
   help configset_aliases
   help configset_tmpdir
   help createlist
   help default
   help mj_confirm
   help mj_email
   help mj_enqueue
   help mj_queuerun
   help mj_shell
   help mj_shutdown
   help mj_trigger
   help mj_wwwadm
   help mj_wwwusr

This is the "configset_debug" 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@openbsd.org.

For assistance, please contact the openbsd.org administrators.

Sign In

Sign Out

Mailing Lists

Unsubscribe or Change Settings

Help