Some key features for this release include:0.8.7d
-bug#0001310: Feature request for poller.php- single host polling
-bug#0001313: Spine takes an excessive amount of time timing out failed tcp pings
-bug#0001358: (cacti + spine) svn. Using snmp v3 constantly get "value: U", whereas snmpget returns correct value
-bug#0001379: Ping.c might send more then retry_count icmp packages
-bug#0001381: configure script distributed with cacti-spine-0.8.7c is broken
-bug#0001420: PCOMMAND: Poller[0] Host[80] WARNING: Recache Event Detected for Host
-bug: A host that for some reason can not initialize snmp can cause a segfault
-bug: When using nifty popen, when the script times out, attempt to kill it
-bug: Under some platforms tcp and udp ping unresponsive
-bug: Availability messaging incorrect for snmpv3 hosts
-bug: TCP Pings that receive a connection refused are good pings
-bug: Avoid segmentation faults when Reindex table issues are found
-bug: When performing snmp_get's, dont assume no error means non-null response
-bug: Some snmp agents don't getnext on '.1' and need another oid '.1.3'
-bug: Net-snmp versioning breaks snmpV3
-bug: Use system level snmp_retries variable instead of 3
-feature: Add one additional debug message to the poller code to track data sources polled
-feature: Add more config paths for packagers
-feature: Allow specification of an optional hostlist instead of first and last hostid's
-feature: Integrate more tightly with boost by allowing writing directly to the boost output table
-feature: Complete implementation poller_id field for people using a poller_id for polling.
1) The ability for the specification of a poller_id other than the default
2) The ability to specify a hostlist as opposed to a range of host ids.
3) The ability for spine to write directly to the boost table when running boost
All of these features allow for more flexibility that I plan for forthcoming releases of Cacti and distributed polling.
The boost feature will not be exploitable until Boost 2.5 is released though. For now, it's just there waiting.
There have been several other changes that affect snmpv3 that cover changes that tend to occur within the net-snmp product as it's implementation of snmpv3 matures.
I have also made changes to the way TCP, UDP, and ICMP pings function to make them more reliable and to generate less traffic. In addition, Spine now properly recognizes the difference between "Ping AND SNMP", and "Ping OR SNMP".
Bottom line is, that outside of the support for multiple pollers, I will pretty soon be working only on making the code faster, and to use less connections.
Enjoy, and if inspired, please donate.
TheWitness