-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Changes between mon-1.2.0- and mon-1.2.0-release
Wed Jun  6 07:45:35 EDT 2007
- -----------------------------------------------

- -Bunch of fixes from Augie Schwer:

 Added RPM spec update to do a "chkconfig on" in the post install, and fixed a
path bug in S99mon

 Fix config parsing of unack_summary, added docs for the option in the man page

 Fix display of ack'd services in mon.cgi

 Fix -p/-P option problem in mon.monitor

 Fix nntp.monitor "-f" option

 Allow snpp.alert to "use strict"

- -added "-m" to http.monitor to match header/content with regex
 by Jim Trocki

- -added hard timeout patch to msql-mysql.monitor
 by Arkadiusz Miskiewicz

- -added fix to ftp.monitor to handle multiline reply after quit command
 by Arkadiusz Miskiewicz

- -fix to fping.monitor to correct parsing of fping 2.2b1 output. It prints
 lines like "ICMP Host Unreachable from" to stderr, but to stdout it
 prints "(host) is unreachable", and the regex was matching both, which
 is wrong.
 by Tim Berger

- -added -u option, "UnexpectedHop", "AlertMessage", to traceroute.monitor
 by Jon Meek

- -updated output formatting in ntpdate.monitor
 by Jon Meek

- -added local-syslog.monitor
 by Jon Meek

- -added --okstring, Cache-Control http header, --debuglog, to 
http_tppnp.monitor
 by Jon Meek

- -updates to smtp3.monitor, --alarmtime, --maxfailtime
 by Jon Meek

- -fixed "disable host" behavior. if a host was the only member of a hostgroup,
 that watch would be disabled, but that host would not be disabled in other
 hostgroups. the correct behavior is that a host will be disabled individually
 in all hostgroups, and if it is the only memeber of a hostgroup, the watch
 associated with that hostgroup will be disabled. enabling the host again undoes
 all of that. the behavior of disabling the watch is useful so that disabling a
 host in a single-hosted hostgroup does not inadvertently leave an empty
 hostgroup, which will generate log warnings when services are run against it.
 reported by Ed Ravin


Changes between mon-1.0.0pre3 and mon-1.0.0pre4
Tue Aug  3 08:02:35 EDT 2004
- -----------------------------------------------

- -when allow_empty_group is not set and no host arguments
 to pass to a monitor, the interval wasn't being reset so
 it would spam the syslog with lots of "no host arguments"
 messages. this is fixed.

- -in reset_timer, there was a chance that _timer could get
 set to a negative value, which is not right. fixed it.

- -fixed the bug where lots of mon processes could accumulate if the
 exec of an alert failed. also fixed error handling of failed
 alerts.

- -added "show failures only" button to mon.cgi to speed it up.
 by Ed Ravin <[EMAIL PROTECTED]>

- -small permissions fix to rpm spec file

- -added MON_CFBASEDIR variable to monitor and alert
 environment, which is set to the value of "cfbasedir" in the
 config file.

- -removed unfinished snmp trap handling stuff. it doesn't work at all,
 and it's misleading to people even though the man page says it doesn't
 work.

- -added monitor_duration and monitor_running output to opstatus detail
 in monshow

Changes between mon-1.0.0pre1 and mon-1.0.0pre3
Mon Jul 12 09:12:29 EDT 2004
- -----------------------------------------------

- -changed README to refer to the new, more sensible name for the perl module
 client, which is mon-client

- -applied eric's updates to INSTALL and added a mention of monshow and mon.cgi 
as
 the web interfaces

- -added eric's rpm spec file (i removed the patches because they are no longer
 needed)

- -added lmb's syslog.monitor (a nifty hack)

- -added 'alertevery strict' code and docs, updated the README and INSTALL to
 mention CVS, updated CREDITS

- -incorporated mon.cgi 1.52

- -minor addition to alert behavior explanation in mon.8

- -in dialin.monitor.wrap.c, return the exit status of execv (if it fails, that 
is)

- -fixed path to perl in file_change.monitor and smtp3.monitor

- -added some rcs tags to identify the file versions

- -handle_trap_timeout now calls process_event, and it works fine with
 alert/upalert/alertevery/etc. as shown by my testing

- -received traps now reset the trap timeout counter, and fixed some
 other stuff wrt trap timeouts

- -added sub process_event and made proc_cleanup and handle_trap use it
 so that the alert mgmt code is shared rather than in two places. i tested
 as much of it as i could and all seems to work well now, especially
 upalert, alertafter, alertevery with traps.

- -added per-service "_monitor_duration" variable which records how many
 seconds the previous monitor took to execute. this is available via
 "list opstatus". if no monitor has executed yet then the value is -1.

- -added per-service "_monitor_running" variable whose value is 0 or 1
 depending on whether the monitor is currently running for that service.

- -removed gunk from handle_trap regarding the various TRAP_COLDSTART, etc.
 processing, since most of it was a bad idea anyway, or at least as far as
 i could tell. traps and their exit values are now processed exactly as
 monitors are, which simplifies things greatly and adds to more intuitive
 functionality. this means the "spc" value in a trap is now ignored.

- -fixed some args processing in call_alert

- -fixed a bug which would prevent alerts or upalerts
 from being sent when call alerts is passed the "output"
 argument whose value is undef

- -remove usage of parse_line in trap processing
 (backported from mon 1.1 code)

- -make esc_str escape spaces in order to be compatible with monperl-1-0-0pre1

- -added list of all possible client commands to moncmd

- -added --community to set the snmp community in reboot.monitor

- -patch to traceroute.monitor from meekj
    added StateDir, TracerouteOptions, StopAt config options
    some bugfixes to config file parsing
    reap children to avoid defunct processes
    added timeout alarm

- -up_rtt.monitor
 added -r to log individual rtts, better error reporting for tcp and udp check




Changes between mon-0.99.3-47 and mon-1.0.0pre1
- -----------------------------------------------
Fri Jun 18 10:35:18 EDT 2004

- -removed nonsensical unless statement which would conditionally set the op
 status to STAT_OK. it should be set unconditionally

- -added "strict" option to alertevery

- -changed protocol to escape spaces to coincide with the change in Mon::Client



Changes between mon-0.99.2 and mon-0.99.3
Fri Jun 11 10:55:27 EDT 2004
- --------------------------------------------

- -updated lpd.monitor

- -added "watch" parameter to monshow
 submitted by Joe Rhett <[EMAIL PROTECTED]>

- -xedia-ipsec-tunnel.monitor now understands the new
 OIDs for sysObjectID.0 in the newer versions of the software

- -fixed exclude_period parsing problem reported by Konstantin 'Kastus' Shchuka
<[EMAIL PROTECTED]>
 and Jeroen Moors <[EMAIL PROTECTED]>

- -fixed a setlogsock problem reported by Gilles Lamiral <[EMAIL PROTECTED]>
 added AIX to the systems which require setlogsock

- -added "clientallow" restriction (trockij renamed it that from serverallow)
 by Ed Ravin <[EMAIL PROTECTED]>

- -added monfailures to clients directory, contributed
 by Ed Ravin <[EMAIL PROTECTED]>

- -patch to fping.monitor which catches more error messages from fping
 by Ed Ravin <[EMAIL PROTECTED]>

- -patch for minor *bsd startup nits
 by Ed Ravin <[EMAIL PROTECTED]>

- -patch to msql-mysql.monitor to support the more typical summary/detail output
format.
 by Ed Ravin <[EMAIL PROTECTED]>

- -patch to phttp.monitor which corrects the uninitialized variable error
 by Ed Ravin <[EMAIL PROTECTED]>

- -patch to phttp.monitor to show more detail in regexp failures
 by Erik Inge Bolsø <[EMAIL PROTECTED]>

- -patch to imap.monitor to report the usual summary followed by details,
 and clarify some error messages for a couple of situations
 by Ed Ravin <[EMAIL PROTECTED]>

- -adjust for some current fping output (ICMP host unreachable),
 correct the docs for failure_interval (which is currently listed as a period
 def rather than a service def)
 from Debian users, submitted by Roderick Schertler <[EMAIL PROTECTED]>

- -another patch to fping.monitor to catch ICMP Time Exceeded failure,
 submitted by John Nelson <[EMAIL PROTECTED]>

- -MON_DESCRIPTION now supplied to monitors

- -added "-f" to etc/S99mon

- -taint fix for perl 5.8 in monshow from Roderick Schertler <[EMAIL PROTECTED]>

- -added trace.monitor, and alternate route path monitor

- -changed ftp.monitor to detect no ftp server when socket opened okay.
 submitted by Dan Kendall <[EMAIL PROTECTED]>

- -updates to ftp.monitor to show detail of ftp conversation

- -added irc.alert

- -added dns-query.monitor

- -mysql.monitor - fix for deprecation of _ListTables
 by Aled Treharne <[EMAIL PROTECTED]>

- -updated smtp.monitor to output detail

- -added "version => 2" to monitors which use
 the net-snmp module so that they work with net-snmp 5.0.6

- -minor documentation updates

- -fixed a bug with the CGI invocation of monshow which would
 yield the error message "premature end of script headers" when you "drilled
 down". bug reported by Hugh Caley <[EMAIL PROTECTED]>

- -mail.alert includes the service description in the body

- -fix for alertafter timer, fix for upalertafter feature
 sent by Adrian Chung <[EMAIL PROTECTED]>

- -fix phttp.monitor for RFC compliance, uses \r\n everywhere in its requests.
 Just \n leads to a "400 Bad Request" on IIS 6.0 in native mode.
 sent by Erik Inge Bolsø <[EMAIL PROTECTED]>

- -fixed reboot.monitor and asyncreboot.monitor to handle counter roll-overs

- -_upalertafterinterval typo fix from Michael Rademacher <[EMAIL PROTECTED]>

- -fix to phttp.monitor for EINPROGRESS from Erik Inge Bolsø
<[EMAIL PROTECTED]>

- -updated file_change.monitor from Jon Meek <[EMAIL PROTECTED]>

- -dtlog a bug where blank lines from the dtlog are being output to the
 client, and the client is interpreting the timestamp as zero. fixed by
 David Nolan <[EMAIL PROTECTED]>

- -fixed qpage.alert:
    Only the first pager gets notified when there is more than one listed for a
qpage.alert.
    The problem is that qpage returns 0 for failure and 1 for success which is
    backwards from what the alert routine thinks will happen.
    submitted by <[EMAIL PROTECTED]>

- -updated nntp.monitor to support authentication
 submitted by Kai Schaetzl/conactive.com

- -unbuffered monerrfile, maybe it'll work

- -fixed trap auth problem, auth.cf parsing bug
 submitted by [EMAIL PROTECTED]

- -updated mon.8 to explain how to set environment variables
 for each service to be passed to monitors and alerts. also
 removed the wording that the client handling is iterative
 (it is not).

- -updated netappfree.monitor, submitted
 by Ed Ravin <[EMAIL PROTECTED]>

- -patch to fix broken upalerts
 submitted by Daniel Fenert <[EMAIL PROTECTED]>

- -patch to dns.monitor for added functionality
 Added -serial_threshold command line argument to allow the zone serials
 between the master and the slaves by that much, at most.  Necessary to
 avoid spurious errors during zone propagation.  High thresholds are
 typically unnecessary, but when using Dynamic DNS, with zones that update
 hundreds if not thousands of times an hour, they can be off by quite a bit
 but still be OK.  If propagation completely fails, eventually we'll exceed
 the threshold.

 Added a mode for monitoring caching only name servers.  Give the
 -caching_only argument, and then instead of -zone and -master arguments,
 you specify -query arguments, which are of the form record[:type].  (With
 A records being the default type)  So you might specify '-query
 myzone.com:MX -query myzone.com:A -query _servicename._udp.myzone.com:SRV'
 Every server will be queried for each request, and must return a valid
 response.  But the records will NOT be cross checked against each other,
 as various round-robin DNS situations may cause the different servers to
 have different data.

 Fixed some error reporting code to format the output better

 Changed the script exit value to be the highest count of how many servers
 failed on a single query.  (I.e. if three servers are queried, for 20
 records, the highest error code possible is 3, not 20 as it was before)


 I found all of these changes to be necessary in our environment, and none
 of them greatly change the original behavior, so I figured they were worth
 submitting.  I would just submit a diff, but a context diff was actually
 BIGGER then just sending the whole file...

 submitted by David Nolan <[EMAIL PROTECTED]>

- -fixed tiny bug in the cmdline operation of monshow which was causing
 the unexpected "No non-switch args expected" which was reported by
 <[EMAIL PROTECTED]>

- -connect STDIN to /dev/null upon daemonization even if monerrfile
 is specified.

- -added the "monerrfile" documentation to mon.8 and explained
 the "all" directive in auth.cf

- --
________________________________________________________________________
 Dario Minnucci (a.k.a. midget)
 Phone: (+34) 902021030 | Fax: (+34) 902024417 | 24/7: (+34) 807429057
 Email: [EMAIL PROTECTED] | URL: http://www.midworld.net/midget/
 Key fingerprint = 6DDB 5487 7F6D 89D4 5D9C  33C7 D181 DD7A 6C42 8272

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGmreh0YHdemxCgnIRAkoKAJ96ydrOmk+xFtxW0794PydYKjKazwCgjFrb
sNfEWVsrKoAAc98RV6fMHtc=
=iqKP
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to