I've upgraded a Pi-hole VM to Beta 5 and am now want to update my pihole-cloudsync
script to work with the updated gravity.db
approach to storing Pi-hole's info.
The original version of my script copied all the relevant files (whitelist, blacklist, adlist, regex) from /etc/pihole
to a local private git repo called my-pihole-lists
before doing its comparisons and synching. I didn't bother stopping stopping the pihole-FTL service in the original script while copying the files (the script runs pihole -g when complete to pick up the updates). But with the updated version of the script I'm working on today, I'm wondering whether I need to stop the pihole-FTL
process while copying the gravity.db
file into or out of the /etc/pihole
directory. Is that worth doing? It would mean the Pi-hole in question wouldn't resolve DNS requests for however long it took for the file operation to complete, so I'd rather not mess with it if it's not necessary to do so. Thanks for any insights!