debian/ 0000775 0000000 0000000 00000000000 12264570667 007207 5 ustar debian/copyright 0000664 0000000 0000000 00000015043 11765710114 011131 0 ustar This package was debianized by Henrik Stoerner There are a few things you should check before you begin to install Xymon.
-Dont be scared of the number of items here - it is likely that you already have
+Don't be scared of the number of items here - it is likely that you already have
most or all of it in place.Prerequisites - before you install Xymon
A webbrowser capable of handling HTML 4, JavaScript and CSS
@@ -34,10 +34,10 @@
IPC mechanisms (shared memory, semaphores) - that should be just about anything
Unix-like you are likely to have.
Xymon uses 8 shared memory segments, ranging in size from 32 KB to 512 KB (2336 KB total) in the default configuration; and 8 sets of 3 semaphores. Experience shows that -some systems need tuning to provide the necessary IPC ressources that Xymon uses. +some systems need tuning to provide the necessary IPC resources that Xymon uses. Specifically, when installing on Solaris you must increase the "shmseg" kernel parameter from the default 6 to at least 8. Since other programs on your system may also use shared memory, a higher value may be required. See http://www.xymon.com/archive/2005/08/msg00183.html for more information about these issues.
Index: xymon/docs/known-issues.html =================================================================== --- xymon.orig/docs/known-issues.html 2012-06-12 17:12:06.000000000 +0200 +++ xymon/docs/known-issues.html 2012-06-15 13:12:18.000000000 +0200 @@ -84,7 +84,7 @@Xymon uses some kernel ressources - semaphores and shared memory. +
Xymon uses some kernel resources - semaphores and shared memory. If you get the following error message in xymonlaunch.log when trying to start Xymon:
Index: xymon/docs/manpages/man8/xymonproxy.8.html =================================================================== --- xymon.orig/docs/manpages/man8/xymonproxy.8.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man8/xymonproxy.8.html 2012-06-15 14:09:29.000000000 +0200 @@ -68,7 +68,7 @@
@@ -89,18 +89,18 @@
-
-
MRTG by default uses its own fileformat for the data files, and continuously generates PNG- or GIF-images of the data. This is a -waste of ressources - most of the time, these images are never seen. +waste of resources - most of the time, these images are never seen. This was in fact one of the reasons that RRDtool was developed, to separate the data-collection from the graph generation.
Index: xymon/xymonproxy/xymonproxy.8 =================================================================== --- xymon.orig/xymonproxy/xymonproxy.8 2012-06-12 17:12:22.000000000 +0200 +++ xymon/xymonproxy/xymonproxy.8 2012-06-15 14:02:39.000000000 +0200 @@ -48,7 +48,7 @@ .IP "--listen=LOCALIP[:PORT]" Specifies the IP-adress where xymonproxy listens for incoming -connections. By default, xymonproxy listens on all IP-adresses +connections. By default, xymonproxy listens on all IP-addresses assigned to the host. If no portnumber is given, port 1984 will be used. @@ -69,18 +69,18 @@ .IP "--lqueue=N" Size of the listen-queue where incoming connections can queue up before being processed. This should be large to -accomodate bursts of activity from clients. Default: 512. +accommodate bursts of activity from clients. Default: 512. .IP "--daemon" -Run in daemon mode, i.e. detach and run as a background proces. +Run in daemon mode, i.e. detach and run as a background process. This is the default. .IP "--no-daemon" -Runs xymonproxy as a foreground proces. +Runs xymonproxy as a foreground process. .IP "--pidfile=FILENAME" -Specifies the location of a file containing the proces-ID -of the xymonproxy daemon proces. Default: /var/run/xymonproxy.pid. +Specifies the location of a file containing the process-ID +of the xymonproxy daemon process. Default: /var/run/xymonproxy.pid. .IP "--logfile=FILENAME" Sends all logging output to the specified file instead of stderr. @@ -88,7 +88,7 @@ .IP "--log-details" Log details (IP-address, message type and hostname) to the logfile. This can also be enabled and disabled at run-time by sending the -xymonproxy proces a SIGUSR1 signal. +xymonproxy process a SIGUSR1 signal. .IP "--debug" Enable debugging output. @@ -126,13 +126,13 @@ The number of other messages (data, notes, ack, query, ...) messages received from a client. -.IP "Proxy ressources - Connection table size" +.IP "Proxy resources - Connection table size" This is the number of connection table slots in the proxy. This measures the number of simultaneously active requests that the proxy has handled, and so gives an idea about the peak number of clients that the proxy has handled simultaneously. -.IP "Proxy ressources - Buffer space" +.IP "Proxy resources - Buffer space" This is the number of KB memory allocated for network buffers. .IP "Timeout details - reading from client" Index: xymon/xymonproxy/xymonproxy.c =================================================================== --- xymon.orig/xymonproxy/xymonproxy.c 2012-06-12 17:12:06.000000000 +0200 +++ xymon/xymonproxy/xymonproxy.c 2012-06-15 14:02:46.000000000 +0200 @@ -241,7 +241,7 @@ unsigned long msgs_recovered = 0; struct timespec timeinqueue = { 0, 0 }; - /* Dont save the output from errprintf() */ + /* Don'T save the output from errprintf() */ save_errbuf = 0; memset(&laddr, 0, sizeof(laddr)); @@ -354,7 +354,7 @@ printf("\t--lqueue=N : Listen-queue size\n"); printf("\t--daemon : Run as a daemon\n"); printf("\t--no-daemon : Do not run as a daemon\n"); - printf("\t--pidfile=FILENAME : Save proces-ID of daemon to FILENAME\n"); + printf("\t--pidfile=FILENAME : Save process-ID of daemon to FILENAME\n"); printf("\t--logfile=FILENAME : Log to FILENAME instead of stderr\n"); printf("\t--debug : Enable debugging output\n"); printf("\n"); @@ -491,7 +491,7 @@ } p = stentry->buf; - p += sprintf(p, "combo\nstatus %s green %s Proxy up %s\n\nxymonproxy for Xymon version %s\n\nProxy statistics\n\nIncoming messages : %10lu (%lu msgs/second)\nOutbound messages : %10lu\n\nIncoming message distribution\n- Combo messages : %10lu\n- Status messages : %10lu\n Messages merged : %10lu\n Resulting combos : %10lu\n- Other messages : %10lu\n\nProxy ressources\n- Connection table size : %10d\n- Buffer space : %10lu kByte\n", + p += sprintf(p, "combo\nstatus %s green %s Proxy up %s\n\nxymonproxy for Xymon version %s\n\nProxy statistics\n\nIncoming messages : %10lu (%lu msgs/second)\nOutbound messages : %10lu\n\nIncoming message distribution\n- Combo messages : %10lu\n- Status messages : %10lu\n Messages merged : %10lu\n Resulting combos : %10lu\n- Other messages : %10lu\n\nProxy resources\n- Connection table size : %10d\n- Buffer space : %10lu kByte\n", proxyname, timestamp, runtime_s, VERSION, msgs_total, (msgs_total - msgs_total_last) / (now - laststatus), msgs_delivered, @@ -665,7 +665,7 @@ currmsg = nextmsg; } while (currmsg); - /* We dont do anymore with this conn_t */ + /* We don't do anymore with this conn_t */ cwalk->state = P_CLEANUP; break; } Index: xymon/docs/manpages/man1/xymonnet.1.html =================================================================== --- xymon.orig/docs/manpages/man1/xymonnet.1.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man1/xymonnet.1.html 2012-06-15 13:24:26.000000000 +0200 @@ -115,7 +115,7 @@ deprecated and should not be used.
Index: xymon/xymond/xymond.c =================================================================== --- xymon.orig/xymond/xymond.c 2012-06-12 17:12:22.000000000 +0200 +++ xymon/xymond/xymond.c 2012-06-15 13:37:01.000000000 +0200 @@ -62,7 +62,7 @@ #define DISABLED_UNTIL_OK -1 /* - * The absolute maximum size we'll grow our buffers to accomodate an incoming message. + * The absolute maximum size we'll grow our buffers to accommodate an incoming message. * This is really just an upper bound to squash the bad guys trying to data-flood us. */ #define MAX_XYMON_INBUFSZ (10*1024*1024) /* 10 MB */ @@ -1004,7 +1004,7 @@ { /* * This routine takes care of finding existing status log records, or - * (if they dont exist) creating new ones for an incoming status. + * (if they don't exist) creating new ones for an incoming status. * * "msg" contains an incoming message. First list is of the form "KEYWORD host,domain.test COLOR" */ @@ -1053,7 +1053,7 @@ colstr = strtok(NULL, " \t"); /* ... and the color (if any) */ if (colstr) { *color = parse_color(colstr); - /* Dont create log-entries if we get a bad color spec. */ + /* Don't create log-entries if we get a bad color spec. */ if (*color == -1) createlog = 0; } else createlog = 0; @@ -1262,7 +1262,7 @@ if (!modifyonly && log->modifiers) { /* * Original status message - check if there is an active modifier for the color. - * We dont do this for status changes triggered by a "modify" command. + * We don't do this for status changes triggered by a "modify" command. */ modifier_t *mwalk; int mcolor = -1; @@ -1375,7 +1375,7 @@ } if (log->acktime > now) { - /* Dont need to do anything about an acked test */ + /* Don't need to do anything about an acked test */ } else { /* The acknowledge has expired. Clear the timestamp and the message buffer */ @@ -1588,7 +1588,7 @@ log->histsynced = 1; /* - * Dont update the log->lastchange timestamp while DOWNTIME is active. + * Don't update the log->lastchange timestamp while DOWNTIME is active. * (It is only seen as active if the color has been forced BLUE). */ if (!log->downtimeactive && (log->oldcolor != newcolor)) { @@ -1738,7 +1738,7 @@ * * We must determine the color based ONLY on the modifications that * have been reported. - * The reason we dont include the original status color in the scan + * The reason we don't include the original status color in the scan * is because the modifiers override the original status - and they * can make it both worse (green -> red) or better (red -> green). * @@ -2030,7 +2030,7 @@ newack = (ackinfo_t *)malloc(sizeof(ackinfo_t)); } else { - /* Drop the old data so we dont leak memory */ + /* Drop the old data so we don't leak memory */ dbgprintf("Dropping old ackinfo data: From %s, msg=%s\n", newack->ackedby, newack->msg); if (newack->ackedby) xfree(newack->ackedby); if (newack->msg) xfree(newack->msg); @@ -3187,7 +3187,7 @@ } /* - * We dont validate the ID, because "notes" may also send messages + * We don't validate the ID, because "notes" may also send messages * for documenting pages or column-names. And the "usermsg" stuff can be * anything in the "ID" field. So we just insist that there IS an ID. */ Index: xymon/xymond/xymond_worker.c =================================================================== --- xymon.orig/xymond/xymond_worker.c 2012-06-12 17:12:06.000000000 +0200 +++ xymon/xymond/xymond_worker.c 2012-06-15 13:38:06.000000000 +0200 @@ -389,7 +389,7 @@ /* idlemsg is used to return the idle message in case of timeouts. */ idlemsg = strdup("@@idle\n"); - /* We dont want to block when reading data. */ + /* We don't want to block when reading data. */ fcntl(inputfd, F_SETFL, O_NONBLOCK); } @@ -414,7 +414,7 @@ endpos = NULL; } - seqnum = 0; /* After skipping, we dont know what to expect */ + seqnum = 0; /* After skipping, we don't know what to expect */ } startagain: @@ -472,7 +472,7 @@ if (needmoredata) { if (maymove && (bufleft < EXTRABUFSPACE)) { - /* Buffer is almost full - move data to accomodate a large message. */ + /* Buffer is almost full - move data to accommodate a large message. */ dbgprintf("Moving %d bytes to start of buffer\n", usedbytes); memmove(buf, startpos, usedbytes); startpos = buf; @@ -585,7 +585,7 @@ if (!locatorid) { /* * Get and check the message sequence number. - * We dont do this for network based workers, since the + * We don't do this for network based workers, since the * sequence number is globally generated (by xymond) * but a network-based worker may only see some of the * messages (those that are not handled by other network-based Index: xymon/xymonnet/xymonnet.1 =================================================================== --- xymon.orig/xymonnet/xymonnet.1 2012-06-12 17:12:22.000000000 +0200 +++ xymon/xymonnet/xymonnet.1 2012-06-15 13:24:19.000000000 +0200 @@ -90,7 +90,7 @@ deprecated and should not be used. .IP --dns=[ip|only|standard] -Determines how xymonnet finds the IP adresses of the hosts to test. +Determines how xymonnet finds the IP addresses of the hosts to test. By default (the "standard"), xymonnet does a DNS lookup of the hostname to determine the IP address, unless the host has the "testip" tag, or the DNS lookup fails. @@ -236,7 +236,7 @@ variable in .I xymonserver.cfg(5). .br -If not specifed, xymonnet uses the CONNTEST environment +If not specified, xymonnet uses the CONNTEST environment variable to determine if it should perform the ping test or not. So if you prefer to use another tool to implement ping checks, either set the CONNTEST environment variable @@ -499,7 +499,7 @@ .br In practice, the maximum size of a single Xymon message sets a limit - the default value for the maximum message -size is 32 KB, but that will easily accomodate 100 status +size is 32 KB, but that will easily accommodate 100 status messages per transmission. So if you want to experiment with this setting, I suggest starting with a value of 10. Index: xymon/docs/manpages/man1/report.cgi.1.html =================================================================== --- xymon.orig/docs/manpages/man1/report.cgi.1.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man1/report.cgi.1.html 2012-06-15 13:17:36.000000000 +0200 @@ -22,7 +22,7 @@ report.cgi is invoked as a CGI script via the report.sh CGI wrapper. It triggers the generation of a Xymon availability -report for the timeperiod specified by the CGI paramaters. +report for the timeperiod specified by the CGI parameters.
report.cgi is passed a QUERY_STRING environment variable with the following parameters: Index: xymon/docs/manpages/man8/xymond.8.html =================================================================== --- xymon.orig/docs/manpages/man8/xymond.8.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man8/xymond.8.html 2012-06-15 13:21:48.000000000 +0200 @@ -81,7 +81,7 @@
By default, any host can send status-updates. If this option is used, then status-updates are accepted only if they are sent by one of the -IP-adresses listed here, or if they are sent from the IP-address of the +IP-addresses listed here, or if they are sent from the IP-address of the host that the updates pertains to (this is to allow Xymon clients to send in their own status updates, without having to list all clients here). So typically you will need to list your servers running network tests here.
-The format of this option is a list of IP-adresses, optionally with a
+The format of this option is a list of IP-addresses, optionally with a
network mask in the form of the number of bits. E.g. if you want to
accept status-updates from the host 172.16.10.2, you would use
Index: xymon/docs/manpages/man8/xymond_alert.8.html
===================================================================
--- xymon.orig/docs/manpages/man8/xymond_alert.8.html 2012-06-12 17:12:22.000000000 +0200
+++ xymon/docs/manpages/man8/xymond_alert.8.html 2012-06-15 13:17:42.000000000 +0200
@@ -82,7 +82,7 @@
--group=GROUPNAME
-The GROUPNAME paramater is a groupid string from the analysis.cfg
+The GROUPNAME parameter is a groupid string from the analysis.cfg
file.
Index: xymon/web/report.cgi.1
===================================================================
--- xymon.orig/web/report.cgi.1 2012-06-12 17:12:22.000000000 +0200
+++ xymon/web/report.cgi.1 2012-06-15 13:16:39.000000000 +0200
@@ -8,7 +8,7 @@
\fBreport.cgi\fR
is invoked as a CGI script via the report.sh CGI wrapper.
It triggers the generation of a Xymon availability
-report for the timeperiod specified by the CGI paramaters.
+report for the timeperiod specified by the CGI parameters.
report.cgi is passed a QUERY_STRING environment variable with the
following parameters:
Index: xymon/xymond/xymond.8
===================================================================
--- xymon.orig/xymond/xymond.8 2012-06-12 17:12:22.000000000 +0200
+++ xymon/xymond/xymond.8 2012-06-15 13:20:45.000000000 +0200
@@ -63,7 +63,7 @@
.IP "--listen=IP[:PORT]"
Specifies the IP-address and port where xymond will listen for incoming
connections. By default, xymond listens on IP 0.0.0.0 (i.e. all IP-
-adresses available on the host) and port 1984.
+addresses available on the host) and port 1984.
.IP "--daemon"
xymond is normally started by
@@ -126,7 +126,7 @@
are pushed to the CLICHG channel. If this option is specified with
no parameter list, all status columns that go into an alert state
will trigger the client data to be sent to the CLICHG channel. If
-a paramater list is added to this option, only those status columns
+a parameter list is added to this option, only those status columns
listed in the list will cause the client data to be sent to the
CLICHG channel. Several column names can be listed, separated by
commas. If all columns are given as "!COLUMNNAME", then all status
@@ -138,12 +138,12 @@
By default, any host can send status-updates. If this option is used,
then status-updates are accepted only if they are sent by one of the
-IP-adresses listed here, or if they are sent from the IP-address of the
+IP-addresses listed here, or if they are sent from the IP-address of the
host that the updates pertains to (this is to allow Xymon clients to send in their
own status updates, without having to list all clients here). So typically
you will need to list your servers running network tests here.
-The format of this option is a list of IP-adresses, optionally with a
+The format of this option is a list of IP-addresses, optionally with a
network mask in the form of the number of bits. E.g. if you want to
accept status-updates from the host 172.16.10.2, you would use
.br
Index: xymon/xymond/xymond_alert.8
===================================================================
--- xymon.orig/xymond/xymond_alert.8 2012-06-12 17:12:22.000000000 +0200
+++ xymon/xymond/xymond_alert.8 2012-06-15 13:17:14.000000000 +0200
@@ -56,7 +56,7 @@
The SECONDS parameter is the duration of the alert in seconds.
.br
.BI "--group=GROUPNAME"
-The GROUPNAME paramater is a groupid string from the analysis.cfg
+The GROUPNAME parameter is a groupid string from the analysis.cfg
file.
.br
.BI "--time=TIMESTRING"
Index: xymon/xymond/xymond_sample.c
===================================================================
--- xymon.orig/xymond/xymond_sample.c 2012-06-12 17:12:06.000000000 +0200
+++ xymon/xymond/xymond_sample.c 2012-06-15 13:36:08.000000000 +0200
@@ -52,7 +52,7 @@
* You can have a timeout when waiting for new
* messages. If it happens, you will get a "@@idle\n"
* message with sequence number 0.
- * If you dont want a timeout, just pass a NULL for the timeout parameter.
+ * If you don't want a timeout, just pass a NULL for the timeout parameter.
*/
timeout = (struct timespec *)(malloc(sizeof(struct timespec)));
timeout->tv_sec = (atoi(argv[argi]+10));
@@ -89,8 +89,8 @@
* All messages have a sequence number ranging from 1-999999.
*
*
- * The first paramater is the channel you're handling - this is used
- * to determine the needed input buffer size. If you dont know what
+ * The first parameter is the channel you're handling - this is used
+ * to determine the needed input buffer size. If you don't know what
* channel you're handling, use C_LAST and you'll get a buffer large
* enough for the largest channel.
*
Index: xymon/README
===================================================================
--- xymon.orig/README 2012-06-12 17:12:05.000000000 +0200
+++ xymon/README 2012-06-15 13:22:24.000000000 +0200
@@ -82,7 +82,7 @@
or on the web http://lists.xymon.com/mailman/listinfo/xymon
-Please note that mail sent from adresses that are not subscribed
+Please note that mail sent from addresses that are not subscribed
to the list need to go through a moderator approval, and therefore
may not show up on the list for some time.
Index: xymon/RELEASENOTES
===================================================================
--- xymon.orig/RELEASENOTES 2012-06-12 17:12:22.000000000 +0200
+++ xymon/RELEASENOTES 2012-06-15 13:20:01.000000000 +0200
@@ -210,8 +210,8 @@
Modem-bank testing ("dialup" host definition) does not work
===========================================================
Previous versions of Xymon supported the Big Brother "dialup"
-host definition for pinging a range of IP-adresses, e.g. a
-modem-bank or a pool of IP-adresses handed out by a DHCP server.
+host definition for pinging a range of IP-addresses, e.g. a
+modem-bank or a pool of IP-addresses handed out by a DHCP server.
This feature is not supported in Xymon 4.2, but may re-appear
in a different form in a later version.
(Note: This has nothing to do with the "dialup" directive
Index: xymon/client/localclient.cfg
===================================================================
--- xymon.orig/client/localclient.cfg 2012-06-15 13:07:39.000000000 +0200
+++ xymon/client/localclient.cfg 2012-06-15 14:00:37.000000000 +0200
@@ -257,7 +257,7 @@
# the output from netstat. This is typically "10.0.0.1:80" for the IP
# 10.0.0.1, port 80. Or "*:80" for any local address, port 80.
# NB: The Xymon clients normally report only the numeric data for
-# IP-adresses and port-numbers, so you must specify the port
+# IP-addresses and port-numbers, so you must specify the port
# number (e.g. "80") instead of the service name ("www").
# "state" causes only the sockets in the specified state to be included;
# it is usually LISTEN or ESTABLISHED.
@@ -312,7 +312,7 @@
# located in the hosts.cfg file, via the hosts' page/subpage/subparent
# directives. This can be convenient to pick out all hosts on a specific page.
#
-# Rules can be dependant on time-of-day, using the standard Xymon syntax
+# Rules can be dependent on time-of-day, using the standard Xymon syntax
# (the hosts.cfg(5) about the NKTIME parameter). E.g. "TIME=W:0800:2200"
# applied to a rule will make this rule active only on week-days between
# 8AM and 10PM.
Index: xymon/common/hosts.cfg.5
===================================================================
--- xymon.orig/common/hosts.cfg.5 2012-06-15 13:07:39.000000000 +0200
+++ xymon/common/hosts.cfg.5 2012-06-15 13:22:01.000000000 +0200
@@ -103,11 +103,11 @@
on other hosts as well.
.IP multihomed
-Tell Xymon that data from the host can arrive from multiple IP-adresses.
+Tell Xymon that data from the host can arrive from multiple IP-addresses.
By default, Xymon will warn if it sees data for one host coming from
-different IP-adresses, because this usually indicates a mis-configuration
+different IP-addresses, because this usually indicates a mis-configuration
of the hostname on at least one of the servers involved. Some hosts
-with multiple IP-adresses may use different IP's for sending data to
+with multiple IP-addresses may use different IP's for sending data to
Xymon, however. This tag disables the check of source IP when receiving
data.
@@ -723,9 +723,9 @@
decides the testname for the connectivity test.
.IP "conn={best,|worst,}IP1[,IP2...]"
-This adds additional IP-adresses that are pinged during the
+This adds additional IP-addresses that are pinged during the
normal "conn" test. So the normal "conn" test must be enabled
-(the default) before this tag has any effect. The IP-adresses
+(the default) before this tag has any effect. The IP-addresses
listed here are pinged in addition to the main IP-address.
When multiple IP's are pinged, you can choose if ALL IP's
Index: xymon/common/xymonclient.cfg.5
===================================================================
--- xymon.orig/common/xymonclient.cfg.5 2012-06-12 17:12:22.000000000 +0200
+++ xymon/common/xymonclient.cfg.5 2012-06-15 13:22:13.000000000 +0200
@@ -15,7 +15,7 @@
Chosen when the Xymon client was compiled.
.IP XYMSERVERS
-List of IP-adresses of Xymon servers. Data will be sent to
+List of IP-addresses of Xymon servers. Data will be sent to
all of the servers listed here. This setting is only used if
XYMSRV=0.0.0.0.
Index: xymon/common/xymonserver.cfg.5
===================================================================
--- xymon.orig/common/xymonserver.cfg.5 2012-06-12 17:12:22.000000000 +0200
+++ xymon/common/xymonserver.cfg.5 2012-06-15 13:24:30.000000000 +0200
@@ -341,9 +341,9 @@
Default: $XYMONSERVERIP
.IP XYMSERVERS
-List of IP-adresses. Clients and network test tools will try to
+List of IP-addresses. Clients and network test tools will try to
send status reports to a Xymon server running on each of these
-adresses. This setting is only used if XYMSRV=0.0.0.0.
+addresses. This setting is only used if XYMSRV=0.0.0.0.
.IP XYMONDPORT
The portnumber for used to contact the
@@ -665,7 +665,7 @@
the maximum number of rows before repeating the column headings
on a webpage. This sets the default value for the
.I xymongen(1)
-"--maxrows" option; if the command-line option is also specifed,
+"--maxrows" option; if the command-line option is also specified,
then it overrides this environment variable. Note that unlike
Jeff's patch, xymongen implements this for both the "All non-green"
page and all other pages (xymon.html, subpages, critical.html).
Index: xymon/docs/manpages/man1/xymonping.1.html
===================================================================
--- xymon.orig/docs/manpages/man1/xymonping.1.html 2012-06-12 17:12:22.000000000 +0200
+++ xymon/docs/manpages/man1/xymonping.1.html 2012-06-15 14:00:34.000000000 +0200
@@ -13,7 +13,7 @@
@@ -24,18 +24,18 @@ is used for ping testing of the hosts monitored by the xymon(7) -monitoring system. It reads a list of IP adresses from stdin, +monitoring system. It reads a list of IP addresses from stdin, and performs a "ping" check to see if these hosts are alive. It is normally invoked by the xymonnet(1) utility, which performs all of the Xymon network tests.
-Optionally, if a list of IP-adresses is passed as command-line +Optionally, if a list of IP-addresses is passed as command-line arguments, it will ping those IP's instead of reading them from stdin.
-xymonping only handles IP-adresses, not hostnames. +xymonping only handles IP-addresses, not hostnames.
xymonping was inspired by the fping(1) @@ -46,10 +46,10 @@ of "fping -Ae".
xymonping probes multiple systems in parallel, and the runtime -is therefore mostly dependant on the timeout-setting and the +is therefore mostly dependent on the timeout-setting and the number of retries. With the default options, xymonping takes approximately 18 seconds to ping all hosts (tested with an -input set of 1500 IP adresses). +input set of 1500 IP addresses).
Example: Go yellow if more than 20% swap is used, and red if more than 40% swap is used or the actual memory utilisation exceeds -90%. Dont alert on physical memory usage. +90%. Don't alert on physical memory usage.
@@ -437,12 +437,12 @@ "addr" is a (partial) local address specification in the format used on the output from netstat.
@@ -811,9 +811,9 @@ decides the testname for the connectivity test.
When multiple IP's are pinged, you can choose if ALL IP's Index: xymon/docs/manpages/man5/xymonclient.cfg.5.html =================================================================== --- xymon.orig/docs/manpages/man5/xymonclient.cfg.5.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man5/xymonclient.cfg.5.html 2012-06-15 13:21:30.000000000 +0200 @@ -29,7 +29,7 @@ Chosen when the Xymon client was compiled.
Index: xymon/docs/manpages/man5/xymonserver.cfg.5.html =================================================================== --- xymon.orig/docs/manpages/man5/xymonserver.cfg.5.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man5/xymonserver.cfg.5.html 2012-06-15 13:24:23.000000000 +0200 @@ -392,9 +392,9 @@ Default: $XYMONSERVERIP
When something breaks, you want to know about it. Since you probably -dont have the Xymon webpages in view all of the time, Xymon can +don't have the Xymon webpages in view all of the time, Xymon can generate alerts to draw your attention to problems. Alerts can go out as e-mail, or Xymon can run a script that takes care of activating a pager, sending an SMS, or however you prefer to get alerted.
@@ -172,7 +172,7 @@ with Xymon.Say you have a long list of hosts or e-mail adresses that you want to use several times throughout the +
Say you have a long list of hosts or e-mail addresses that you want to use several times throughout the
alerts.cfg file. Do you have to write the full list every time ? No:
$WEBHOSTS=%(www|intranet|support|mail).foo.com @@ -185,7 +185,7 @@
$UNIXSUPPORT=MAIL unixsupport@foo.com TIME=*:0800:1600 SERVICE=cpu,disk,memory @@ -205,7 +205,7 @@There are rules ... and exceptions: IGNORE
A common scenario is where you handle most of the alerts with a wildcard rule, but -there is just that one exception where you dont want any cpu alerts +there is just that one exception where you don't want any cpu alerts from the marketing server on Thursday afternoon. Then it is time for the IGNORE recipient:
Index: xymon/rpm/xymon-client.default =================================================================== --- xymon.orig/rpm/xymon-client.default 2012-06-12 17:12:06.000000000 +0200 +++ xymon/rpm/xymon-client.default 2012-06-15 13:21:55.000000000 +0200 @@ -2,7 +2,7 @@ # You MUST set the list of Xymon servers that this # client reports to. -# It is good to use IP-adresses here instead of DNS +# It is good to use IP-addresses here instead of DNS # names - DNS might not work if there's a problem. # # E.g. (a single Xymon server) Index: xymon/web/svcstatus-info.c =================================================================== --- xymon.orig/web/svcstatus-info.c 2012-06-12 17:12:06.000000000 +0200 +++ xymon/web/svcstatus-info.c 2012-06-15 13:20:28.000000000 +0200 @@ -24,7 +24,7 @@ #include#include -/* The following is for the DNS lookup we perform on DHCP adresses */ +/* The following is for the DNS lookup we perform on DHCP addresses */ #include #include #include Index: xymon/xymond/analysis.cfg.5 =================================================================== --- xymon.orig/xymond/analysis.cfg.5 2012-06-15 13:07:39.000000000 +0200 +++ xymon/xymond/analysis.cfg.5 2012-06-15 13:38:00.000000000 +0200 @@ -121,7 +121,7 @@ .sp Example: Go yellow if more than 20% swap is used, and red if more than 40% swap is used or the actual memory utilisation exceeds -90%. Dont alert on physical memory usage. +90%. Don't alert on physical memory usage. .IP .nf MEMSWAP 20 40 @@ -359,12 +359,12 @@ "addr" is a (partial) local address specification in the format used on the output from netstat. .IP "EXLOCAL=addr" -Exclude certain local adresses from the rule. +Exclude certain local addresses from the rule. .IP "REMOTE=addr" "addr" is a (partial) remote address specification in the format used on the output from netstat. .IP "EXREMOTE=addr" -Exclude certain remote adresses from the rule. +Exclude certain remote addresses from the rule. .IP "STATE=state" Causes only the sockets in the specified state to be included, "state" is usually LISTEN or ESTABLISHED but can be any socket state reported by @@ -374,7 +374,7 @@ .LP "addr" is typically "10.0.0.1:80" for the IP 10.0.0.1, port 80. Or "*:80" for any local address, port 80. Note that the Xymon clients -normally report only the numeric data for IP-adresses and port-numbers, +normally report only the numeric data for IP-addresses and port-numbers, so you must specify the port number (e.g. "80") instead of the service name ("www"). .br Index: xymon/xymond/etcfiles/analysis.cfg =================================================================== --- xymon.orig/xymond/etcfiles/analysis.cfg 2012-06-15 13:07:39.000000000 +0200 +++ xymon/xymond/etcfiles/analysis.cfg 2012-06-15 14:00:29.000000000 +0200 @@ -255,7 +255,7 @@ # the output from netstat. This is typically "10.0.0.1:80" for the IP # 10.0.0.1, port 80. Or "*:80" for any local address, port 80. # NB: The Xymon clients normally report only the numeric data for -# IP-adresses and port-numbers, so you must specify the port +# IP-addresses and port-numbers, so you must specify the port # number (e.g. "80") instead of the service name ("www"). # "state" causes only the sockets in the specified state to be included; # it is usually LISTEN or ESTABLISHED. @@ -310,7 +310,7 @@ # located in the hosts.cfg file, via the hosts' page/subpage/subparent # directives. This can be convenient to pick out all hosts on a specific page. # -# Rules can be dependant on time-of-day, using the standard Xymon syntax +# Rules can be dependent on time-of-day, using the standard Xymon syntax # (the hosts.cfg(5) about the NKTIME parameter). E.g. "TIME=W:0800:2200" # applied to a rule will make this rule active only on week-days between # 8AM and 10PM. Index: xymon/xymonnet/xymonping.1 =================================================================== --- xymon.orig/xymonnet/xymonping.1 2012-06-12 17:12:22.000000000 +0200 +++ xymon/xymonnet/xymonping.1 2012-06-15 14:00:25.000000000 +0200 @@ -2,23 +2,23 @@ .SH NAME xymonping \- Xymon ping tool .SH SYNOPSIS -.B "xymonping [--retries=N] [--timeout=N] [IP-adresses]" +.B "xymonping [--retries=N] [--timeout=N] [IP-addresses]" .SH DESCRIPTION .I xymonping(1) is used for ping testing of the hosts monitored by the .I xymon(7) -monitoring system. It reads a list of IP adresses from stdin, +monitoring system. It reads a list of IP addresses from stdin, and performs a "ping" check to see if these hosts are alive. It is normally invoked by the .I xymonnet(1) utility, which performs all of the Xymon network tests. -Optionally, if a list of IP-adresses is passed as command-line +Optionally, if a list of IP-addresses is passed as command-line arguments, it will ping those IP's instead of reading them from stdin. -xymonping only handles IP-adresses, not hostnames. +xymonping only handles IP-addresses, not hostnames. xymonping was inspired by the .I fping(1) @@ -28,10 +28,10 @@ of "fping -Ae". xymonping probes multiple systems in parallel, and the runtime -is therefore mostly dependant on the timeout-setting and the +is therefore mostly dependent on the timeout-setting and the number of retries. With the default options, xymonping takes approximately 18 seconds to ping all hosts (tested with an -input set of 1500 IP adresses). +input set of 1500 IP addresses). .SH SUID-ROOT INSTALLATION REQUIRED xymonping needs to be installed with suid-root privileges, Index: xymon/build/setup-newfiles.c =================================================================== --- xymon.orig/build/setup-newfiles.c 2012-06-12 17:12:05.000000000 +0200 +++ xymon/build/setup-newfiles.c 2012-06-15 13:27:39.000000000 +0200 @@ -67,7 +67,7 @@ if (stat(destfn, &st) == 0) { /* Destination file exists, see if it's a previous version */ - if (sumbuf == NULL) continue; /* No md5-data, dont overwrite an existing file */ + if (sumbuf == NULL) continue; /* No md5-data, don't overwrite an existing file */ if (!S_ISREG(st.st_mode)) continue; fd = fopen(destfn, "r"); if (fd == NULL) continue; @@ -99,13 +99,13 @@ infd = fopen(srcfn, "r"); if (infd == NULL) { - /* Dont know how this can happen, but .. */ + /* Don't know how this can happen, but .. */ fprintf(stderr, "Cannot open input file %s: %s\n", srcfn, strerror(errno)); return 1; } outfd = fopen(destfn, "w"); if (outfd == NULL) { - /* Dont know how this can happen, but .. */ + /* Don't know how this can happen, but .. */ fprintf(stderr, "Cannot create output file %s: %s\n", destfn, strerror(errno)); return 1; } Index: xymon/client/logfetch.c =================================================================== --- xymon.orig/client/logfetch.c 2012-06-12 17:12:05.000000000 +0200 +++ xymon/client/logfetch.c 2012-06-15 13:42:56.000000000 +0200 @@ -37,7 +37,7 @@ #include "libxymon.h" /* Is it ok for these to be hardcoded ? */ -#define MAXCHECK 102400 /* When starting, dont look at more than 100 KB of data */ +#define MAXCHECK 102400 /* When starting, don't look at more than 100 KB of data */ #define MAXMINUTES 30 #define POSCOUNT ((MAXMINUTES / 5) + 1) #define LINES_AROUND_TRIGGER 5 Index: xymon/client/msgcache.c =================================================================== --- xymon.orig/client/msgcache.c 2012-06-12 17:12:05.000000000 +0200 +++ xymon/client/msgcache.c 2012-06-15 13:42:52.000000000 +0200 @@ -205,7 +205,7 @@ addtobuffer(conn->msgbuf, client_response); /* - * Dont drop the client response data. If for some reason + * Don't drop the client response data. If for some reason * the "client" request is repeated, he should still get * the right answer that we have. */ @@ -284,7 +284,7 @@ struct sigaction sa; int opt; - /* Dont save the output from errprintf() */ + /* Don't save the output from errprintf() */ save_errbuf = 0; memset(&laddr, 0, sizeof(laddr)); Index: xymon/client/xymonclient-freebsd.sh =================================================================== --- xymon.orig/client/xymonclient-freebsd.sh 2012-06-12 17:12:05.000000000 +0200 +++ xymon/client/xymonclient-freebsd.sh 2012-06-15 13:43:01.000000000 +0200 @@ -45,7 +45,7 @@ echo "[ports]" (netstat -na -f inet; netstat -na -f inet6) | grep "^tcp" echo "[ps]" -# Dont use "args". "command" works also in FreeBSD 4.x. +# Don't use "args". "command" works also in FreeBSD 4.x. ps -ax -ww -o pid,ppid,user,start,state,pri,pcpu,cputime,pmem,rss,vsz,command # $TOP must be set, the install utility should do that for us if it exists. Index: xymon/client/xymonclient-sunos.sh =================================================================== --- xymon.orig/client/xymonclient-sunos.sh 2012-06-12 17:12:05.000000000 +0200 +++ xymon/client/xymonclient-sunos.sh 2012-06-15 13:42:40.000000000 +0200 @@ -25,7 +25,7 @@ # Print the root filesystem first, with the header, and those fs's that have the same type. ROOTFSTYPE=`/bin/df -n / | awk '{print $3}'` /bin/df -F $ROOTFSTYPE -k -# Then see what fs types are in use, and weed out those we dont want. +# Then see what fs types are in use, and weed out those we don't want. FSTYPES=`/bin/df -n -l|cut -d: -f2 | awk '{print $1}'|egrep -v "^${ROOTFSTYPE}|^proc|^fd|^mntfs|^ctfs|^devfs|^objfs|^nfs|^lofs"|sort|uniq` set $FSTYPES while test "$1" != ""; do Index: xymon/client/xymonclient.cfg.DIST =================================================================== --- xymon.orig/client/xymonclient.cfg.DIST 2012-06-15 13:07:38.000000000 +0200 +++ xymon/client/xymonclient.cfg.DIST 2012-06-15 13:43:04.000000000 +0200 @@ -6,7 +6,7 @@ PATH="/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/lib/xymon/client/bin" # PATH setting for the client scripts. -# You normally dont need to modify anything below here +# You normally don't need to modify anything below here XYMONDPORT="1984" # Portnumber where xymond listens XYMONCLIENTHOME="/usr/lib/xymon/client" XYMONHOME="$XYMONCLIENTHOME" # Directory for the Xymon client files Index: xymon/common/tasks.cfg.5 =================================================================== --- xymon.orig/common/tasks.cfg.5 2012-06-12 17:12:22.000000000 +0200 +++ xymon/common/tasks.cfg.5 2012-06-15 13:42:35.000000000 +0200 @@ -89,7 +89,7 @@ The \fBGROUP\fR keyword can be used to limit the number of tasks that may run simultaneously. E.g. if you are generating multiple -pagesets of webpages, you dont want them to run at the same time. +pagesets of webpages, you don't want them to run at the same time. Putting them into a GROUP will cause xymonlaunch to delay the start of new tasks, so that only one task will run per group. You can change the limit by defining the group before the tasks, with Index: xymon/docs/configure.txt =================================================================== --- xymon.orig/docs/configure.txt 2012-06-12 17:12:05.000000000 +0200 +++ xymon/docs/configure.txt 2012-06-15 13:42:04.000000000 +0200 @@ -105,7 +105,7 @@ top-level directory. I can set this up if you tell me what group-ID your webserver runs with. This is typically 'nobody' or 'apache' or 'www-data' -If you dont know, just hit ENTER and we will handle it later. +If you don't know, just hit ENTER and we will handle it later. What group-ID does your webserver use ? www-data Index: xymon/docs/manpages/man1/combostatus.1.html =================================================================== --- xymon.orig/docs/manpages/man1/combostatus.1.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man1/combostatus.1.html 2012-06-15 13:42:26.000000000 +0200 @@ -62,7 +62,7 @@ combostatus.
- --no-update
- -Dont send any status messages - instead, the result of the combotests +Don't send any status messages - instead, the result of the combotests is simply dumped to stdout. Useful for debugging.
Index: xymon/docs/manpages/man1/xymongen.1.html =================================================================== --- xymon.orig/docs/manpages/man1/xymongen.1.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man1/xymongen.1.html 2012-06-15 13:42:23.000000000 +0200 @@ -550,7 +550,7 @@ The syntax is identical to the normal "page" and "subpage" directives in hosts.cfg, but the directive is prefixed with -the pageset name. Dont put any hosts in-between the page +the pageset name. Don't put any hosts in-between the page and subpage directives - just add all the directives at the top of the hosts.cfg file.
Index: xymon/docs/manpages/man5/alerts.cfg.5.html =================================================================== --- xymon.orig/docs/manpages/man5/alerts.cfg.5.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man5/alerts.cfg.5.html 2012-06-15 13:42:19.000000000 +0200 @@ -170,7 +170,7 @@ This is used to define a recipient that does NOT trigger any alerts, and also terminates the search for more recipients. It is useful if you have a rule that handles most alerts, but -there is just that one particular server where you dont want cpu alerts on Monday morning. +there is just that one particular server where you don't want cpu alerts on Monday morning. Note that the IGNORE recipient always has the STOP flag defined, so when the IGNORE recipient is matched, no more recipients will be considered. So the location of this recipient in your set of recipients is important. Index: xymon/docs/manpages/man5/tasks.cfg.5.html =================================================================== --- xymon.orig/docs/manpages/man5/tasks.cfg.5.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man5/tasks.cfg.5.html 2012-06-15 13:42:09.000000000 +0200 @@ -118,7 +118,7 @@The GROUP keyword can be used to limit the number of tasks that may run simultaneously. E.g. if you are generating multiple -pagesets of webpages, you dont want them to run at the same time. +pagesets of webpages, you don't want them to run at the same time. Putting them into a GROUP will cause xymonlaunch to delay the start of new tasks, so that only one task will run per group. You can change the limit by defining the group before the tasks, with Index: xymon/docs/manpages/man8/xymon-mailack.8.html =================================================================== --- xymon.orig/docs/manpages/man8/xymon-mailack.8.html 2012-06-12 17:12:22.000000000 +0200 +++ xymon/docs/manpages/man8/xymon-mailack.8.html 2012-06-15 13:42:31.000000000 +0200 @@ -85,7 +85,7 @@ Load environment from FILENAME, usually xymonserver.cfg.
- --debug
- -Dont send a message to xymond, but dump the message to +Don't send a message to xymond, but dump the message to stdout.
Did you install a client ? The Xymon client package is installed automatically only on the Xymon server - on other systems, you must build the client package by running Xymon's configure-script with @@ -228,7 +228,7 @@ Big Brother at the www.deadcat.net archive, and these will typically work without modifications if you run them in Xymon. Sometimes a few minor tweaks are needed - the Xymon mailing list -can help you if you dont know how to go about that.
+can help you if you don't know how to go about that.But if you have something unique you need to test, writing an extension script is pretty simple. You need to figure out some things:
First, you should realize that this is not a fully automated -proces. You will need to do some work yourself - especially with +process. You will need to do some work yourself - especially with the handling of alerts.
Index: xymon/xymond/etcfiles/snmpmibs.cfg
===================================================================
--- xymon.orig/xymond/etcfiles/snmpmibs.cfg 2012-06-12 17:12:06.000000000 +0200
+++ xymon/xymond/etcfiles/snmpmibs.cfg 2012-06-15 14:09:04.000000000 +0200
@@ -39,7 +39,7 @@
Used = HOST-RESOURCES-MIB::hrStorageUsed /rrd:GAUGE
[hrtask]
-# hrtask is the closest you can get to a proces-listing
+# hrtask is the closest you can get to a process-listing
keyidx (HOST-RESOURCES-MIB::hrSWRunName)
keyidx [HOST-RESOURCES-MIB::hrSWRunPath]
keyidx
+Note: libssl 1.0.0 in Debian deprecates the use of SSLv2 and hence https2 will
+fall back to testing SSLv3.