Hello!
A cursory look through some of the code indicates that some voucher info is stored in the config during a graceful shutdown/reboot. Even that wont help with ram disks, or if there is a power loss.
Check on the requirements that forced you to move from 2.4.5 to 2.5.x and see if any of those can be worked around.
Try building a fresh 2.5.x without ram disks and see how it works.
Moving back to "no ram disks" after initially using them might work with a little scripting.
Using the current rc.backup* and rc.restore* scripts as a template for manually saving and restoring the /var/db data...
While ram disks are still on...
rc.backup_db
#!/bin/sh
#
: ${DBPATH:=/var/db}
: ${CF_CONF_PATH:=/cf/conf}
: ${RAM_Disk_Store:=${CF_CONF_PATH}/RAM_Disk_Store}
# Save the logs database to the RAM disk store.
if [ -d "${DBPATH}" ]; then
echo -n "Saving DB to RAM disk store...";
[ -f "${RAM_Disk_Store}/db.tgz" ] && /bin/rm -f "${RAM_Disk_Store}/db.tgz"
if [ ! -d "${RAM_Disk_Store}" ]; then
mkdir -p "${RAM_Disk_Store}"
fi
/usr/bin/tar -czf "${RAM_Disk_Store}/db.tgz" -C / "${DBPATH#/}/"
echo "done.";
fi
Turn off ram disks, reboot, manually run...
rc.restore_db
#!/bin/sh
#
: ${CF_CONF_PATH:=/cf/conf}
: ${RAM_Disk_Store:=${CF_CONF_PATH}/RAM_Disk_Store}
/usr/bin/tar -xzf "${RAM_Disk_Store}/db.tgz" -C / 2>&1
Restart captive portal and see if it picks up your newly restored /var/db
The standard system rc.restore_ramdisk_store might even catch & restore the db.tgz you created if it runs when rams disks are off (???).
This is a highly experimental process with lots of unknowns. Use at your own risk.
Maybe someone with more/better knowledge of the startup/shutdown and ram disk operations could chime in.
John
