| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Include Logs
Restoring the RAM disk as soon as it is available will make it easier to include additional content that needs to persist across reboots for packages etc.
Include the logs in the RAM disk store so they will persist across reboots.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
If ramdisk is enabled keep a copy of the alias tables to restore at boot time. Otherwise unpredictable behavior may occur due to some aliases not being available when the firewall rules load.
Because alias tables are typically somewhat static, the following strategies are employed to keep write cycles to a minimum for SSD and flash drive type devices friendliness.
1) Back up during reboot/shutdown only if a backup copy of the alias table does not already exists. This is typically during the reboot when ramdisk is first enabled.
2) Update the backup copy only when the alias table is updated with a new download, typically 1 or more days, as configured in the firewall alias.
|
|
|
|
|
|
| |
- Add a new script, read_global_var, that returns the value of any item
contained in global array $g
- Replace all grep and sed magic from shell scripts
|
|
|
|
|
|
| |
Create /usr/local/sbin/read_xml_tag.sh, that will read a xml tag from
config file using xmllint. Replace all direct read using cat, grep, sed,
... by this script
|
|
|
|
| |
product_name
|
|
|