Digimer daca6c887b * This contains a fairly major change to how time stamps are handled. All INSERT and UPDATE calls now generate a new timestamp via Database->refresh_timestamp, instead of using 'sys::database::timestamp'. This was done in responce to finding a bug where tables in a database differed in both counts of public and private schemas (ip_addresses table, specifically) that failed to resync because the timestamps were re-used too often. ... * WIP - Continuing work on the new anvil-manage-server tool. * Updated Database->get_anvils() to load information on the files available on each Anvil! system. * Updated Database->insert_or_update_network_interfaces() to no longer take the 'timestamp' parameter. * Removed all logging from Database->refresh_timestamp() to speed it up, given how often it will be called now. Signed-off-by: Digimer <digimer@alteeve.ca>		2021-06-08 15:23:15 -04:00
..
Account.pm	* This contains a fairly major change to how time stamps are handled. All INSERT and UPDATE calls now generate a new timestamp via Database->refresh_timestamp, instead of using 'sys::database::timestamp'. This was done in responce to finding a bug where tables in a database differed in both counts of public and private schemas (ip_addresses table, specifically) that failed to resync because the timestamps were re-used too often.	2021-06-08 15:23:15 -04:00
Alert.pm	* This contains a fairly major change to how time stamps are handled. All INSERT and UPDATE calls now generate a new timestamp via Database->refresh_timestamp, instead of using 'sys::database::timestamp'. This was done in responce to finding a bug where tables in a database differed in both counts of public and private schemas (ip_addresses table, specifically) that failed to resync because the timestamps were re-used too often.	2021-06-08 15:23:15 -04:00
Cluster.pm	* Updated Tools->catch_sig() to use return code 0 instead of 255 so that systemd doesn't think our daemons failed on stop.	2021-06-05 14:32:26 -04:00
Convert.pm
Database.pm	* This contains a fairly major change to how time stamps are handled. All INSERT and UPDATE calls now generate a new timestamp via Database->refresh_timestamp, instead of using 'sys::database::timestamp'. This was done in responce to finding a bug where tables in a database differed in both counts of public and private schemas (ip_addresses table, specifically) that failed to resync because the timestamps were re-used too often.	2021-06-08 15:23:15 -04:00
DRBD.pm
Email.pm
Get.pm
Job.pm
Log.pm
Network.pm
Remote.pm
ScanCore.pm
Server.pm	* This contains a fairly major change to how time stamps are handled. All INSERT and UPDATE calls now generate a new timestamp via Database->refresh_timestamp, instead of using 'sys::database::timestamp'. This was done in responce to finding a bug where tables in a database differed in both counts of public and private schemas (ip_addresses table, specifically) that failed to resync because the timestamps were re-used too often.	2021-06-08 15:23:15 -04:00
Storage.pm
Striker.pm
System.pm
Template.pm
Validate.pm
Words.pm