features of it:
- As long as the 'sensors' program works correctly, healthd.sh is compatible
with any hardware.
- Very low loading. Just sleeps (like me) most of the time.
- Easily customizable (very simple and short script).
Todo's/wants:
- Syslogging? I couldn't figure out how to syslog from bash shell (yet).
- After one test, it failed to be automatically 'spawned' from a rc.local
script. I did "healthd.sh &", but that didn't seem to work. Ideas?
- a history utility for making pretty plots and such.
- Written in 'C' for better functionality and efficiency?
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@229 7894878c-1315-0410-8ee3-d5d059ff63e0
(from the Greek meaning 'shortcoming').
A word electrical engineers like me learn to know and love.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@223 7894878c-1315-0410-8ee3-d5d059ff63e0
I am trying to create a more-or-less standard documentation format for
doc/chips/* files. I am not quite satisfied with the lm75 and lm78 docs
yet, but it is starting to come. Basically, I want as much information
in it as possible, and to generate most of it automatically. But that is
harder than I though it would be.
Also, a small library bugfix (class problem) and a doc-features fix.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@210 7894878c-1315-0410-8ee3-d5d059ff63e0
This program automatically documents the available features for each chip.
Basically, it translates the data in lib/chips.c back to a human-readable
format.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@208 7894878c-1315-0410-8ee3-d5d059ff63e0
I finally merged in Adrian's man-pages. libsensors.3 is unchanged from his
version; sensors.conf.5 is heavily edited, not because he did a bad job,
but because his source material was not very well written :-). It should
now tell you more about the config file than you ever wanted to know...
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@205 7894878c-1315-0410-8ee3-d5d059ff63e0
Renamed sensors entry from "SiS 5595 Sensor-*" to "sis5595-*"
Added this name in sensors.conf.eg to use lm78 names for inputs.
Small related document updates.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@199 7894878c-1315-0410-8ee3-d5d059ff63e0
integrated LM78, so the driver is only a customized copy of lm78.c
This southbridge can also do i2c, but this not enough documented in
the datasheet. So i2c is currently not supported.
Some cosmetic changes for VIA driver and documentation.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@196 7894878c-1315-0410-8ee3-d5d059ff63e0
Right now, it can detect several adapters: the PIIX4, the VIA Southbridge and
the SIS southbridge. The tough stuff will be the separate devices...
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@195 7894878c-1315-0410-8ee3-d5d059ff63e0
It tries to delete bit-via.o, bit-mb.o, isa.o and piix4.o in the module
install directory.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@194 7894878c-1315-0410-8ee3-d5d059ff63e0
lm_sensors2 source tree. Improvements in VIA driver,
now checks revision code and refuses to load the
module if bit_test (in algo-bit) fails.
(Also fixes previous unsuccessfull CVS commit)
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@187 7894878c-1315-0410-8ee3-d5d059ff63e0
I really hope I did not forget an add or remove. If strange things happen
when you compile, please let me know.
There may still be problems with the EXPORT_* stuff; it seems to work now
for kernel 2.0.36pre19, but it may give trouble for earlier kernels. We
need to check that.
Some i2c modules may be a bit verbose at this moment.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@184 7894878c-1315-0410-8ee3-d5d059ff63e0
