Menu
▾
▴
Tree [c08b42] master / History
| File | Date | Author | Commit |
|---|---|---|---|
| conf | 2014-10-28 |
Craig Small
|
[c96754] Set SNMP correct output |
| docs | 2012-03-28 |
Craig Small
|
[9db64c] minor crontab fix and check_status fix |
| engine | 2015-11-14 |
Craig Small
|
[fe2f17] Use correct fetch DS function |
| htdocs | 2014-10-21 |
Craig Small
|
[e4bdd5] Default to client_id 0 |
| lib | 2016-06-12 |
Craig Small
|
[c08b42] DB: Use the current mysqli PHP API |
| src | 2014-07-31 |
Craig Small
|
[ae4a7e] Adjusted Reachability poller to use popen() |
| AUTHORS | 2011-04-19 |
Craig Small
|
[ab9fb3] engine fixes and logfiles |
| BUGS | 2010-05-27 |
Craig Small
|
[dc30db] moved to top directory |
| Changelog | 2012-11-01 |
Craig Small
|
[9644c4] pgsql importer fixed |
| LICENSE | 2011-02-04 |
Craig Small
|
[2bb5e1] poller cleanup and ipv6 |
| Makefile | 2012-11-01 |
Craig Small
|
[9644c4] pgsql importer fixed |
| README | 2010-05-27 |
Craig Small
|
[dc30db] moved to top directory |
| TODO | 2010-05-27 |
Craig Small
|
[dc30db] moved to top directory |
| notar-list.txt | 2010-05-27 |
Craig Small
|
[dc30db] moved to top directory |
Read Me
README file for JFFNMS
======================
This file contains important information about JFFNMS and should be read
before installing or upgrading JFFNMS.
Upgrading from 0.8.4
--------------------
JFFNMS version 0.8.4 shipped with a serious bug with the database extraction.
The part of the build process that makes the databases differences was
missing, however the database dump worked ok.
This gives us two scenarios:
* You had a pre 0.8.4 (eg 0.8.3) JFFNMS and upgraded, giving you an
unchanged 0.8.3 database.
* You (re)installed jffnms 0.8.4 and used the database dump. You got the
correct database.
The schema for 0.8.4 and 0.8.5 are the same.
This means if you are the first pre-0.8.4 scenario you WILL need to run the SQL update scripts to update your schema, just like you normally should do.
If JFFNMS 0.8.4 was your first database install, your schema is already
current, do NOT update the database (it will error out anyhow).
