Early adopters are always going to get burned if there is an issue.
Packages and SVN are just different ways of distributing software. The former doesn't necessarily guarantee that the code will be any more stable than than updating via the latter.
I think the takeaway here is that if you are going to use FOSS and it has the potential to burn you, then a) don't be an early adopter - let others SVN their kit and get issues fixed before updating yourself and/or b) build a lab and vet any changes yourself before rolling it out en masse.
Sent from my iPhone
On 2013-06-17, at 1:41 PM, Paul Strefling strefli3@gmail.com wrote:
Funny you mention this. Just the other day the hddtemp script brought down one of my Debian machines. Observium's hddtemp script expects nc==nc.traditional which in my case nc==openbsd. nc.openbsd hung at 100% CPU load until the machine self destructed. Good thing we had a backup.
-P
On Jun 17, 2013 10:31 AM, "Nikolay Shopik" shopik@inblock.ru wrote:
Well I doubt observium could be disaster for network as its only reading stuff and not commit anything.
Only disaster could happend and this is when obs stop working and you noticing this late billing for example.
On 17.06.2013 20:53, Tristan Rhodes wrote:
Any powerful and useful tool (like Observium) has the potential to be the worst disaster for a network. Whether from a malicious attack or unintentional bug, these tools are something that keep me up at night (I use them because I think the benefits are worth the risk).
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium