--- name: "mon" section: "1" platform: "linux" package: "mon" version: "0.38.15-1" release: "Debian 2.2 (Potato)" platforms: ["linux"] url: "https://new.carta.tech/mon" --- # mon(1) monitor services for availability, sending alarms upon failures. ## NAME mon - monitor services for availability, sending alarms upon failures. ## SYNOPSIS **mon** \[**lMSv**\] \[**-a** *dir*\] \[**-A** *authfile*\] \[**-b** *dir*\] \[**-B** *dir*\] \[**-c** *config*\] \[**-d** *level*\] \[**-D** *dir*\] \[**-i** *secs*\] \[**-k** *num*\] \[**-l** *dir*\] \[**-m** *num*\] \[**-p** *num*\] \[**-P** *pidfile*\] \[**-r** *delay*\] \[**-s** *dir*\] ## DESCRIPTION **mon** is a general-purpose scheduler for monitoring service availability and triggering alerts upon detecting failures. **mon** was designed to be open in the sense that it supports arbitrary monitoring facilities and alert methods via a common interface, which are easily implemented through shell scripts, Perl scripts, C, or any other language. ## OPTIONS - **-a** *dir* Path to alert scripts. Default is */usr/local/lib/mon/alert.d:alert.d*. Multiple alert paths may be specified by separating them with a colon. Non-absolute paths are taken to be relative to the base directory (*/usr/lib/mon* by default). - **-b** *dir* Base directory for mon. scriptdir, alertdir, and statedir are all relative to this directory unless specified from /. Default is */usr/lib/mon*. - **-B** *dir* Configuration file base directory. All config files are located here, including mon.cf, monusers.cf, and auth.cf. - **-A** *authfile* Authentication configuration file. By default this is */etc/mon/auth.cf* if the */etc/mon* directory exists, or */usr/lib/mon/auth.cf* otherwise. - **-c** *file* Read configuration from *file*. This defaults to */etc/mon/mon.cf* if the */etc/mon* directory exists, otherwise to */etc/mon.cf*. - **-d** *level* Set debug level to *level***.** 0 is the default, it doesn't show any debugging info. Higher numbers show more info (but 1 is the only level used at the moment). - **-D dir** Path to state directory. Default is the first of */var/state/mon*, */var/lib/mon*, and */usr/lib/mon/state.d* which exists. - **-f** Fork and run as a daemon process. This is the preferred way to run **mon**. - **-h** Print help information. - **-i** *secs* Sleep interval, in seconds. Defaults to 1. This shouldn't need to be adjusted for any reason. - **-k** *num* Set log history to a maximum of *num* entries. Defaults to 100. - **-l** Load state from the last saved state file. Currently the only supported saved state is disabled watches, services, and hosts. - **-L dir** Sets the log dir. See also **logdir** in the configuration file. The default is **/var/log/mon** if that directory exists, otherwise **log.d** in the base directory. - **-M** Pre-process the configuration file with the macro expansion package *m4*. - **-m** *num* Set the throttle for the maximum number of processes to *num*. - **-p** *num* Make server listen on port *num*. This defaults to 32777. - **-S** Start with the scheduler stopped. - **-P** *pidfile* Store the server's pid in *pidfile*, the default is the first of */var/run/mon/mon.pid*, */var/run/mon.pid*, and */etc/mon.pid* whose directory exists. An empty value tells **mon** not to use a pid file. - **-r** *delay* Sets the number of seconds used to randomize the startup delay before each service is scheduled. Refer to the global *randstart* variable in the configuration file. - **-s** *dir* Path to monitor scripts. Default is */usr/local/lib/mon/mon.d:mon.d*. Multiple alert paths may be specified by separating them with a colon. Non-absolute paths are taken to be relative to the base directory (*/usr/lib/mon* by default). - **-v** Print version information. ## DEFINITIONS - **monitor** A program which tests for a certain condition, returns either true or false, and optionally produces output to be passed back to the scheduler. Common monitors detect host reachability via ICMP echo messages, or connection to TCP services. - **period** A period in time as interpreted by the Time::Perl module. - **alert** A program which sends a message when invoked by the scheduler. The scheduler calls upon an alert when it detects a failure from a monitor. An alert program accepts a set of command-line arguments from the scheduler, in addition to data via standard input. - **hostgroup** A single host or list of hosts, specified as names or IP addresses. - **service** A collection of parameters used to deal with monitoring a particular resource which is provided by a group. Services are usually modeled after things such as an SMTP server, ICMP echo capability, server disk space availability, or SNMP events. - **watch** A collection of services which apply to a particular group. ## OPERATION When the **mon** scheduler starts, it reads a configuration file to determine the services it needs to monitor. The configuration file defaults to */etc/mon.cf*, and can be specified using the **-c** parameter. If the **-M** option is specified, then the configuration file is pre-processed with *m4*. If the configuration file ends with .m4, the file is also processed by m4 automatically. The scheduler enters a loop which handles client connections, monitor invocations, and failure alerts. Each service has a timer, specified in the configuration file as the **interval** variable, which tells the scheduler how frequently to invoke a monitor process. The scheduler may be temporarily stopped. While it is stopped, client access still functions, but it just doesn't schedule things. This is useful in conjunction while resetting the server, because you can do this: save the hosts and services which are disabled, reset the server with the scheduler stopped, re-disabled those hosts and services, then start the scheduler. It also allows making atomic changes across several client connections. See the **moncmd** man page for more information. ## MONITOR PROGRAMS Monitor processes are invoked with the arguments specified in the configuration file, appended by the hosts from the applicable host group. For example, if the watch group is "servers", which contain the hostnames "smtp", "nntp", and "ns", and the monitor line reads as follows,\ `monitor fping.monitor -t 4000 -r 2`\ then the executable "fping.monitor" will be executed with these parameters:\ `MONITOR_DIR/fping.monitor -t 4000 -r 2 smtp nntp ns`\ MONITOR\_DIR is actually a search path, by default */usr/local/lib/mon/mon.d* then */usr/lib/mon/mon.d*, but it can be overridden by the **-s** option or in the configuration file. If all hosts in the hostgroup have been disabled, then a warning is sent to syslog and the monitor is not run. This behavior may be overridden with the "allow\_empty\_group" option in the service definition. If the final argument to the "monitor" line is ";;" (it must be preceded by whitespace), then the host list will not be appended to the parameter list. In addition to environment variables defined by the user in the service definition, **mon** passes certain variables to monitor process. - **MON\_LAST\_SUMMARY** The first line of the output from the last time the monitor exited. - **MON\_LAST\_OUTPUT** The entire output of the monitor from the last time it exited. - **MON\_LAST\_FAILURE** The [time(2)](/time/2.md) of the last failure for this service. - **MON\_FIRST\_FAILURE** The [time(2)](/time/2.md) of the first time this service failed. - **MON\_LAST\_SUCCESS** The [time(2)](/time/2.md) of the last time this service passed. - **MON\_ALERTTYPE** Has one of the following values: "failure", "up", "startup", "trap", or "traptimeout", and signifies the type of alert which was triggered. This environment variable is meant to supersede the "-u" command-line parameter passed to alert scripts. - **MON\_DESCRIPTION** The description of this service, as defined in the configuration file using the *description* tag. - **MON\_RETVAL** The exit value of the failed monitor. "fping.monitor" should return an exit status of 0 if it completed successfully (found no problems), or nonzero if a problem was detected. The first line of output from the monitor script has a special meaning: it is used as a brief summary of the exact failure which was detected, and is passed to the alert program. All remaining output is also passed to the alert program, but it has no required interpretation. If a monitor for a particular service is still running, and the time comes for **mon** to run another monitor for that service, it will not start another monitor. For example, if the *interval* is 10s, and the monitor does not finish running within 10 seconds, then **mon** will wait until the first monitor exits before running another one. Upon a nonzero exit status, the associated alert program is started, pending the following criteria: If an alert for a specific service is disabled, do not send an alert. If an alert is not within the specified period, record the failure via [syslog(3)](/syslog/3.md) and do not send an alert. If the failure falls within the defined period, and an alert was already sent within the last **alertevery** interval, do not send another alert, *unless* the output from the current monitor program differs from the last monitor process. Otherwise, send an alert using each alert program listed for that period. ## ALERT PROGRAMS Alert programs are found in the path supplied with the **-a** parameter, or in the */usr/local/lib/mon/alert.d* and */usr/lib/mon/alert.d* directories if not specified. They are invoked with the following command-line parameters: - **-s** *service* Service tag from the configuration file. - **-g** *group* Host group name from the configuration file. - **-h** *hosts* The expanded version of the host group, space delimited, but contained in one shell "word". - **-t** *secs* The number of seconds left before another alert will be sent out. - **-u** This option is supplied to an alert only if it is being called as an upalert. The remaining arguments are supplied from the trailing parameters in the configuration file, after the "alert" service parameter. As with monitor programs, alert programs are invoked with environment variables defined by the user in the service definition, in addition to the following which are explicitly set by the server: - **MON\_LAST\_SUMMARY** The first line of the output from the last time the monitor exited. - **MON\_LAST\_OUTPUT** The entire output of the monitor from the last time it exited. - **MON\_LAST\_FAILURE** The [time(2)](/time/2.md) of the last failure for this service. - **MON\_FIRST\_FAILURE** The [time(2)](/time/2.md) of the first time this service failed. - **MON\_LAST\_SUCCESS** The [time(2)](/time/2.md) of the last time this service passed. - **MON\_DESCRIPTION** The description of this service, as defined in the configuration file using the *description* tag. - **MON\_OPSTATUS** The operational status of the service. The first line from standard input must be used as a brief summary of the problem, normally supplied as the subject line of an email, or text sent to an alphanumeric pager. Interpretation of all subsequent lines read from stdin is left up to the monitoring program. The usual parameters are a list of recipients to deliver the notification to. The interpretation of the recipients is not specified, and is up to the alert program. ## CONFIGURATION FILE The configuration file consists of zero or more hostgroup definitions, and one or more watch definitions. Each watch definition may have one or more service definitions. A line beginning with optional leading whitespace and a pound ("#") is regarded as a comment, and is ignored. Lines are parsed as they are read. Long lines may be continued by ending them with a backslash ("\\"). If a line is continued, then the backslash, the trailing whitespace after the backslash, and the leading whitespace of the following line are removed. The end result is assembled into a single line. ### Global Variables The following variables may be set to override compiled-in defaults. Command-line options will have a higher precedence than these definitions. - **alertdir =** *dir* *dir* is the full path to the alert scripts. This is the value set by the **-a** command-line parameter. Multiple alert paths may be specified by separating them with a colon. Non-absolute paths are taken to be relative to the base directory (*/usr/lib/mon* by default). When the configuration file is read, all alerts referenced from the configuration will be looked up in each of these paths, and the full path to the first instance of the alert found is stored in a hash. This hash is only generated upon startup or after a "reset" command, so newly added alert scripts will not be recognized until a "reset" is performed. - **mondir =** *dir* *dir* is the full path to the monitor scripts. This value may also be set by the **-s** command-line parameter. Multiple alert paths may be specified by separating them with a colon. Non-absolute paths are taken to be relative to the base directory (*/usr/lib/mon* by default). When the configuration file is read, all monitors referenced from the configuration will be looked up in each of these paths, and the full path to the first instance of the monitor found is stored in a hash. This hash is only generated upon startup or after a "reset" command, so newly added monitor scripts will not be recognized until a "reset" is performed. - **statedir =** *dir* *dir* is the full path to the state directory. **mon** uses this directory to save various state information. - **logdir =** *dir* *dir* is the full path to the log directory. **mon** uses this directory to save various logs, including the downtime log. - **basedir =** *dir* *dir* is the full path for the state, script, and alert directory. - **authfile =** *file* *file* is the full path to the authentication file. - **authtype =** *type* *type* is the type of authentication to use. If *type* is **getpwnam**, then the standard Unix passwd file authentication method will be used (calls [getpwnam(3)](/getpwnam/3.md) on the user and compares the [crypt(3)](/crypt/3.md)ed version of the password with what it gets from getpwnam). This will not work if shadow passwords are enabled on the system. If *type* is **userfile**, then usernames and hashed passwords are read from *userfile*, which is defined via the **userfile** configuration variable. If *type* is **shadow**, then shadow password may be used (NOT IMPLEMENTED). - **userfile =** *file* This file is used when **authtype** is set to *userfile*. It consists of a sequence of lines of the format **'username : password'**. **password** is stored as the hash returned by the standard Unix [crypt(3)](/crypt/3.md) function. Blank lines and lines beginning with # are ignored. - **snmpport =** *portnum* Set the SNMP port that the server binds to. - **serverbind =** *addr* - **trapbind =** *addr* **serverbind** and **trapbind** specify which address to bind the server and trap ports to, respectively. If these are not defined, the default address is INADDR\_ANY, which allows connections on all interfaces. For security reasons, it could be a good idea to bind only to the loopback interface. - **use SNMP** Turn on SNMP support. - **dtlogfile =** *file* *file* is a file which will be used to record the downtime log. Whenever a service fails for some amount of time and then stop failing, this event is written to the log. If this parameter is not set, no logging is done. The format of the file is as follows (# is a comment and may be ignored): **timenoticed group service firstfail downtime interval summary**. **timenoticed** is the [time(2)](/time/2.md) the service came back up. **group service** is the group and service which failed. **firstfail** is the [time(2)](/time/2.md) when the service began to fail. **downtime** is the number of seconds the service failed. **interval** is the frequency (in seconds) that the service is polled. **summary** is the summary line from when the service was failing. - **dtlogging =** *yes/no* Turns downtime logging on or off. The default is off. - **histlength =** *num* *num* is the the maximum number of events to be retained in history list. The default is 100. This value may also be set by the **-k** command-line parameter. - **historicfile =** *file* If this variable is set, then alerts are logged to *file*, and upon startup, some (or all) of the past history is read into memory. - **historictime =** *timeval* *num* is the amount of the history file to read upon startup. "Now" - *timeval* is read. See the explanation of *interval* in the "Service Definitions" section for a description of *timeval*. - **serverport =** *port* *port* is the TCP port number that the server should bind to. This value may also be set by the **-p** command-line parameter. Normally this port is looked up via [getservbyname(3)](/getservbyname/3.md), and it defaults to 2583. - **trapport =** *port* *port* is the UDP port number that the trap server should bind to. Normally this port is looked up via [getservbyname(3)](/getservbyname/3.md), and it defaults to 2583. - **pidfile =** *path* *path* is the file the sever will store its pid in. This value may also be set by the **-P** command-line parameter. - **maxprocs =** *num* Throttles the number of concurrently forked processes to *num.* The intent is to provide a safety net for the unlikely situation when the server tries to take on too many tasks at once. Note that this situation has only been reported to happen when trying to use a garbled configuration file! You don't want to use a garbled configuration file now, do you? - **cltimeout =** *secs* Sets the client inactivity timeout to *secs.* This is meant to help thwart denial of service attacks or recover from crashed clients. *secs* is interpreted as a "1h/1m/1s" string, where "1m" = 60 seconds. - **randstart =** *secs* When the server starts, normally all services will not be scheduled until the interval defined in the respective service section. This can cause long delays before the first check of a service, and possibly a high load on the server if multiple things are scheduled at the same intervals. This option is used to randomize the scheduling of the first test for all services during the startup period, and immediately after the *reset* command. If *randstart* is defined, the scheduled run time of all services of all watch groups will be a random number between zero and *randstart* seconds. - **dep\_recur\_limit =** *depth* Limit dependency recursion level to *depth*. If dependency recursion (dependencies which depend on other dependencies) tries to go beyond *depth*, then the recursion is aborted and a messages is logged to syslog. The default limit is 10. - **dep\_behavior =** *{a\|m}* **dep\_behavior** controls whether the dependency expression suppresses either the running of alerts or monitors when a node in the dependency graph fails. Read more about the behavior in the "Service Definitions" section below. This is a global setting which controls the default settings for the service-specified variable. ### Hostgroup Entries Hostgroup entries begin with the keyword **hostgroup**, and are followed by a hostgroup tag and one or more hostnames or IP addresses, separated by whitespace. The hostgroup tag must be composed of alphanumeric characters, a dash ("-"), a period ("."), or an underscore ("\_"). Non-blank lines following the first hostgroup line are interpreted as more hostnames. The hostgroup definition ends with a blank line. For example: ``` hostgroup servers nameserver smtpserver nntpserver nfsserver httpserver smbserver hostgroup router_group cisco7000 agsplus ``` ### Watch Group Entries Watch entries begin with a line that starts with the keyword **watch**, followed by whitespace and a single word which normally refers to a pre-defined hostgroup. If the second word is not recognized as a hostgroup tag, a new hostgroup is created whose tag is that word, and that word is its only member. Watch entries consist of one or more service definitions. ### Service Definitions - **service** *servicename* A service definition begins with they keyword **service** followed by a word which is the tag for this service. The components of a service are an interval, monitor, and one or more time period definitions, as defined below. - **interval** *timeval* The keyword **interval** followed by a time value specifies the frequency that a monitor script will be triggered. Time values are defined as "30s", "5m", "1h", or "1d", meaning 30 seconds, 5 minutes, 1 hour, or 1 day. The numeric portion may be a fraction, such as "1.5h" or an hour and a half. This format of a time specification will be referred to as *timeval*. - **traptimeout** *timeval* This keyword takes the same time specification argument as **interval***,* and makes the service expect a trap from an external source at least that often, else a failure will be registered. This is used for a heartbeat-style service. - **trapduration** *timeval* If a trap is received, the status of the service the trap was delivered to will normally remain constant. If **trapduration** is specified, the status of the service will remain in a failure state for the duration specified by *timeval*, and then it will be reset to "success". - **randskew** *timeval* Rather than schedule the monitor script to run at the start of each interval, randomly adjust the interval specified by the **interval** parameter by plus-or-minus **randskew .** The skew value is specified as the **interval** parameter: "30s", "5m", etc... For example if **interval** is 1m, and **randskew** is "5s", then *mon* will schedule the monitor script some time between every 55 seconds and 65 seconds. The intent is to help distribute the load on the server when many services are scheduled at the same intervals. - **monitor** *monitor-name \[arg...\]* The keyword **monitor** followed by a script name and arguments specifies the monitor to run when the timer expires. Shell-like quoting conventions are followed when specifying the arguments to send to the monitor script. The script is invoked from the directory given with the **-s** argument, and all following words are supplied as arguments to the monitor program, followed by the list of hosts in the group referred to by the current watch group. If the monitor line ends with ";;" as a separate word, the host groups are not appended to the argument list when the program is invoked. - **allow\_empty\_group** The **allow\_empty\_group** option will allow a monitor to be invoked even when the hostgroup for that watch is empty because of disabled hosts. The default behavior is not to invoke the monitor when all hosts in a hostgroup have been disabled. - **description** *descriptiontext* The text following **description** is queried by client programs, passed to alerts and monitors via an environment variable. It should contain a brief description of the service, suitable for inclusion in an email or on a web page. - **depend** *dependexpression* The **depend** keyword is used to specify a dependency expression, which evaluates to either true of false, in the boolean sense. Dependencies are actual Perl expressions, and must obey all syntactical rules. The expressions are evaluated in their own package space so as to not accidentally have some unwanted side-effect. If a syntax error is found when evaluating the expression, it is logged via syslog. Before evaluation, the following substitutions on the expression occur: phrases which look like "group:service" are substituted with the value of the current operational status of that specified service. These opstatus substitutions are computed recursively, so if service A depends upon service B, and service B depends upon service C, then service A depends upon service C. Successful operational statuses (which evaluate to "1") are "STAT\_OK", "STAT\_COLDSTART", "STAT\_WARMSTART", and "STAT\_UNKNOWN". This feature can be used to control alerts for services which are dependent on other services, e.g. an SMTP test which is dependent upon the machine being ping-reachable. - **dep\_behavior** *{a\|m}* The evaluation of dependency graphs can control the suppression of either alert or monitor invocations. **Alert suppression**. If this option is set to "a", then the dependency expression will be evaluated after the monitor for the service exits or after a trap is received. An alert will only be sent if the evaluation succeeds, meaning that none of the nodes in the dependency graph indicate failure. **Monitor suppression**. If it is set to "m", then the dependency expression will be evaulated before the monitor for the service is about to run. If the evaulation succeeds, then the monitor will be run. Otherwise, the monitor will not be run and the status of the service will remain the same. ### Period Definitions Periods are used to define the conditions which should allow alerts to be delivered. - **period** *\[label:\] periodspec* A period groups one or more alarms and variables which control how often an alert happens when there is a failure. The **period** keyword has two forms. The first takes an argument which is a period specification from Patrick Ryan's Time::Period Perl 5 module. Refer to "perldoc Time::Period" for more information. The second form requires a label followed by a period specification, as defined above. The label is a tag consisting of an alphabetic character or underscore followed by zero or more alphanumerics or underscores and ending with a colon. This form allows multiple periods with the same period definition. One use is to have a period definition which has no **alertafter** or **alertevery** parameters for a particular time period, and another for the same time period with a different set of alerts that does contain those parameters. - **alertevery** *timeval* The **alertevery** keyword (within a **period** definition) takes the same type of argument as the **interval** variable, and limits the number of times an alert is sent when the service continues to fail. For example, if the interval is "1h", then only the alerts in the period section will only be triggered once every hour. If the **alertevery** keyword is omitted in a period entry, an alert will be sent out every time a failure is detected. By default, if the output of two successive failures changes, then the alertevery interval is overridden. If the word "summary" is the last argument, then only the summary output lines will be considered when comparing the output of successive failures. - **alertafter** *num* - **alertafter** *num timeval* The **alertafter** keyword (within a **period** section) has two forms: only with the "num" argument, or with the "num timeval" arguments. In the first form, an alert will only be invoked after "num" consecutive failures. In the second form, the arguments are a positive integer followed by an interval, as described by the **interval** variable above. If these parameters are specified, then the alerts for that period will only be called after that many failures happen within that interval. For example, if **alertafter** is given the arguments "3 30m", then the alert will be called if 3 failures happen within 30 minutes. - **numalerts** *num* This variable tells the server to call no more than *num* alerts during a failure. The alert counter is kept on a per-period basis, and is reset upon each success. - **comp\_alerts** If this option is specified, then upalerts will only be called if a corresponding "down" alert has been called. - **alert** *alert \[arg...\]* A period may contain multiple alerts, which are triggered upon failure of the service. An alert is specified with the **alert** keyword, followed by an optional **exit** parameter, and arguments which are interpreted the same as the **monitor** definition, but without the ";;" exception. The **exit** parameter takes the form of **exit=x** or **exit=x-y** and has the effect that the alert is only called if the exit status of the monitor script falls within the range of the **exit** parameter. If, for example, the alert line is *alert exit=10-20 mail.alert mis* then *mail-alert* will only be invoked with *mis* as its arguments if the monitor program's exit value is between 10 and 20. This feature allows you to trigger different alerts at different severity levels (like when free disk space goes from 8% to 3%). Alert programs are invoked with the following command-line parameters: - **-s** *service name* The service tag for this failure. - **-g** *hostgroup* The tag of the host group for this service. - **-h** *hostgroup expansion* All of the members in this hostgroup. - **-t** *time* The time (in [**time**(2)](/time/2.md) format) of when this failure condition was detected. - **-l** *alertevery* The number of seconds until the next alarm will be sent. - **-u** This option is supplied to an alert only if it is being called as an upalert. - **upalert** *alert \[arg...\]* An **upalert** is the compliment of an **alert**. An upalert is called when a services makes the state transition from failure to success. The **upalert** script is called supplying the same parameters as the **alert** script, with the addition of the **-u** parameter which is simply used to let an alert script know that it is being called as an upalert. Multiple upalerts may be specified for each period definition. Please note that the default behavior is that an upalert will be sent regardless if there were any prior "down" alerts sent, since upalerts are triggered on a state transition. Set the per-period **comp\_alerts** option to pair upalerts with "down" alerts. - **startupalert** *alert \[arg...\]* A **startupalert** is only called when the **mon** server starts execution. - **upalertafter** *timeval* The **upalertafter** parameter is specified as a string that follows the syntax of the **interval** parameter ("30s", "1m", etc.), and controls the triggering of an **upalert**. If a service comes back up after being down for a time greater than or equal to the value of this option, an **upalert** will be called. Use this option to prevent upalerts to be called because of "blips" (brief outages). ## AUTHENTICATION CONFIGURATION FILE The file specified by the **authfile** variable in the configuration file (or passed via the **-A** parameter) will be loaded upon startup. This file defines restrictions upon which client commands may be executed by which users. It is a text file which consists of comments and command definitions. A comment line begins with optional whitespace followed by pound sign. Blank lines are ignored. A command definition consists of a command, followed by a colon, followed by a comma-separated list of users who may execute the command. The default is that no users may execute any commands. An example configuration file: ``` list: all reset: root,admin loadstate: root savestate: root ``` This means that all clients are able to perform the **list** command, "root" is able to perform "reset", "loadstate", "savestate", and "admin" is able to execute the "reset" command. ## CLIENT-SERVER INTERFACE The server listens on TCP port 32777, which may be overridden using the **-p** *port* option. Commands are a single line each, terminated by a newline. Currently the server is iterative, accepting a single client at a time. This will change in future releases. ## CLIENT INTERFACE COMMANDS See manual page for **moncmd**. ## EXAMPLES The **mon** distribution comes with an example configuration called *example.cf*. Refer to that file for more information. ## SEE ALSO [**moncmd**(1)](/moncmd/1.md), [**Time::Period**(3pm)](/Time::Period/3pm.md) ## HISTORY **mon** was written because I couldn't find anything out there that did just what I needed, and nothing was worth modifying to add the features I wanted. It doesn't have a cool name, and that bothers me because I couldn't think of one. ## BUGS Report bugs to the email address below. ## AUTHOR Jim Trocki \