The Housleys dot Net

UNDER CONSTRUCTION

OpenBSD

Version 0.6.0 is missing a library for compiling on OpenBSD. I am sorry about that. To fix exit Makefile after running ./configure and add -li386 to the LIBS line. I keep saying that I am going to install OpenBSD onto my system. I found the disk space, now I need the time.

OVERVIEW


SECURITY INFORMATION

For information about security and vulnerabilities please see the security page.

LATEST VERSION

Version 0.6.0 is the latest version. This include the capability to execute scripts on both the warn and fail conditions. This version should run on OpenBSD, ISA mode only. It is also reported to compile on DEC Alpha versions of FreeBSD.

TO-DO

Request for Help
Anyone the is good with gd or some other program for creating line graphs on the web or can point me at one please let me know. What I would like to do is create a sample app using healthdc that will plot the values over time.

The following list is roughly in order of my priorities, but not necessarily in the order they will get completed. If you would like to see other features please let me know at jim@thehousleys.net.

  • (Added: v 0.5) Create a program that is able to obtain the current state of all monitored parameters.
  • (Added: v 0.5) Add network capability so a master machine is able to log/monitor the state of all machines.
  • (Added: v 0.6)Create a program to monitor all networked machines.
  • Create a program to monitor all networked machines with a real-time display (maybe something like top).
  • Linux port.
  • (Added: v 0.6.1) Add IPv6 support.
  • Add SNMP support.
  • Be able to configure the number of bad readings before warning and failure.
  • Add hysteresis so borderline values don't bounce and continuously trigger warnings.

  • MRTG

    Here are some examples of using MRTG to record healthd values.

    SOFTWARE

    healthd V0.6.7
    April 5, 2002: OpenBSD needs "_deny_severity" and "_allow_severity"
    	defined for healthdc.
    	Eduardo B. Fonseca 
    
    healthd V0.6.6
    February 4, 2002:  Fix the order of processing of the
    	environment variables by healthdc.  This allows
    	the command line to override the ENV.
    	David McNett 
    
    healthd V0.6.5
    March 14, 2001: Add a -B option to use Vbat for Vcore1
    	with W83782D style chips (Abit BP6).  Submitted by:
    	Trev Roydhouse 
    
    healthd V0.6.4
    January 6, 2001: Fix problems introduced in 0.6.3
            on 4-STABLE and probable 5-CURRENT.
    
    
    healthd V0.6.3
    January 4, 2001: Fix compile on FreeBSD 3.5.1 and others
            that don't have IPv6 stacks.
    
    
    healthd V0.6.2
    November 13, 2000: Fix potential Divide by Zero
    
    
    healthd V0.6.1
    October 10, 2000: Thanks to Archie Cobbs <archie@whistle.com>
    	For submitting a patch for the Winbond W83627HF
    
    October 3, 2000: IANA has assigned me an official port of 1281.
    	That is different for 9669 that was used origionally.
    	-P 9669 can be used to specify the old port number.
    
    September 29, 2000: Thanks to Claus Assmann <ca+healthd@esmtp.org>
    	for another patch to allow ISA mode to work on OpenBSD.
    
    September 14, 2000:
    	Change the printing of daemon error from stderr to using
    	syslog.
    
    	Only enable the reading of the doWarn and doFail settings
    	and the contents of the *_warn and *_fail scripts if
    	compiled with -DFULL_CONFIG or ./configure --enable-full-config.
    	This is because I beleive that the information might provide
    	information that might be useful in exploiting the machine.
    
    September 13, 2000:
    	Protocol 2.0.  Enables obtaining version and configuration
    	information from the running daemon.
    
    September 11, 2000:
    	IPv6 support added to healthd and healthdc.  IPv6
    	support also works for libwrap.
    
    
    healthd V0.6.0
    August 20, 2000: Thanks to Claus Assmann <ca+healthd@esmtp.org>
    	for a patch to allow ISA mode to work on OpenBSD.
    
    	Thanks to Stefan Moeding <s.moeding@ndh.net> for the 
    	origional version of the code to allow external programs
    	to be run on warnings and failures.  It has since then
    	been greatly extended.
    
    healthd V0.5.4 Fixed healthd.sh

    healthd V0.5.3 This is another small update. I dropped an option on install. Minor network code clean up.

    healthd V0.5.2 This is a minor update. The healthd man page was updated. Support for start/stop/reload was added to healthd.sh.

    healthd V0.5.1

    Thanks to  Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
    	For a sample implementation of SIGHUP to re-read the config file.
    
    This version expands upon the networking code. The -L option was added for local-mode, ie no listen-socket is created. A -V option was added to return a version string. Both healthd and healthdc man pages are updated and more complete.

    healthd V0.5

    Thanks to  Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
    	For visually identifing the unknown ASUS "health" chip.
    
    This version is the first to add network monitoring capability. A new program has been added, healthdc. This can be used to read the current values from the healthd running on any networked machine. healthd uses libwrap, if available, to authenticate access. The following could be added to /etc/hosts.access:
    healthd : 192.168.0.0/16 : ALLOW
    healthd : myhouse.network.com : ALLOW
    healthd : ALL : DENY
    

    healthd V0.4.2

    April 26, 2000: Changed ReadConfigFile() & ParseOption() to not display
    	unknown options, instead display the line number.  This prevents
    	the user from using healthd to display files the user doesn't have
    	permission to read.  (thanks: Volker Stolz 
    	<stolz@Pool.Informatik.RWTH-Aachen.DE>)
    
    healthd V0.4.1
    April 9, 2000: Added -c option (thanks: David McNett <nugget@distributed.net>)
    
    healthd V0.4 patch-aa
    March 25, 2000: Fix root exploit (thanks: Valentin Nechayev 
    	<netch@segfault.kiev.au>)
    
    healthd V0.3
    healthd V0.2
    healthd V0.1

    Mail any questions/concerns to webmaster