Let's try avoiding an extra reboot on updating
When doing an update to either base-os or freenasUI, it touches the sentinel files to indicate ix-update should, um, update. This then requires another reboot.
Per conversation with Josh, when doing an update, I believe I can instead do:
yes | /usr/local/bin/python /usr/local/www/freenasUI/manage.py migrate --all --merge --delete-ghost-migrations
So let's try it. (I've done an update using it, and it seems to have worked. But I'd tried this before, and it didn't work, but I was not doing it at the right times, I think.)
#2 Updated by Cyber Jock over 5 years ago
So let me ask this silly question... assuming I have some tunables and sysctls set in the WebGUI, can I expect that without the "extra reboot" they would be properly applied? I thought back in 8.x this was one of the reasons for the extra reboots. So that the user-experience would be such that once the box was "up" for good that all of the WebGUI settings would be properly applied.