you only need to do it once then it "sticks" so no need for a startup script.
I had the 9.004-34 build, and every time the UTM got restarted (power loss or something else) the web proxy stopped working properly. I had to do something, so i started to hunt the issue:
1. restarted the web filtering (http, https, url filtering enabled) - nothing 2. disabled https filtering - some development, but not much 3. enabled https filtering - nothing 4. stopped web filtering - working again 5. enabled web filtering - nothing 6. re-applied local content filter database and restarted web filtering - working! 7. Every time i restarted UTM, indeed sfcontrol download size was the same or higher, but web filtering just didnt' worked without re-applying. Just restarting web filtering from the shell didn't work either.
OK, so re-applying local content filter database worked, so i thought a good startup script will do the job.
Then i thought i could manually upgrade to 9.005-15, developers sad there are major improvements in this area. Done. After the upgrade, i checked the sfcontrol download size, 0. So i re-applied local content filter database. Restarted, checked sfcontrol download size, 0 again. So there is a difference between the two builds, local content filter database is empty after every restart or power loss.
This is why i need the startup script.. Or maybe something else to fix this.
Edit: i could manually back-up the download and re-copying it every time, but this is not a reliable workaround, what if i can't, because i'm not at home? The entire network will be down until i get back..
