summaryrefslogtreecommitdiffstats
path: root/src/etc/rc.backup_rrd.sh
Commit message (Collapse)AuthorAgeFilesLines
* RAM Disk Management - Update I - Eliminate RRD XML Dump/Restore & Alias ↵NOYB2017-01-081-16/+2
| | | | | | | Tables Backup Age Logic Eliminate rrd dump/restore to/from xlm file. Backup and restore the entire /var/db/rrd/ to/from the RAM Disk Store. Add logic to backup alias tables if the backup is older than the table.
* RAM Disk ManagementNOYB2017-01-081-7/+16
| | | | | | | | | | | | | | | 1) Treat the RAM disk more like a permanent storage device with content managed/restored by the system and made available at boot up, before needed by any services. a) Handle saving and restoring RAM disk content at reboot/shutdown/boot centrally in more of a system manged fashion. b) If it's in the RAM disk store it gets restored early in the pfSense startup so it's available for whatever needs to use it. c) Services utilizing RAM disk don't need to be aware that their content is on a RAM disk, and handling content restore individually. 2) Has the benefit of eliminating some issues with the previous code as well. Such as... a) Restoring RRD multiple times during boot, potentially at least 3 times, by rc.newwanip, rc.newwanipv6, and rc.boot. Some even overlapping. b) Not removing the backups if/when not being utilized. Such as on a full install with the RAM disk option not enabled. c) Eliminate some duplicate code. 3) Looking forward. a) The more centrally system managed approach may crack the door open to making it easier to include some of the logs in the RAM disk store. As well as anything else that may be useful/desirable to retain in the RAM disk across reboots.
* Pass specific filename to tar and rm during rrd backupRenato Botelho2017-01-021-3/+4
|
* Remove all calls to conf_mount_r* functionsRenato Botelho2016-10-121-2/+0
|
* Move main pfSense content to src/Renato Botelho2015-08-251-0/+27
OpenPOWER on IntegriCloud