-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do we really need the pihole -g ? #2
Comments
Yes I think you are correct! I'd like to try it out and change it but I can't test it at the moment. I'm setting up my network from the ground up. Have you tried it and it worked? Thank you for your appreciation, I'm really glad it was useful for you! :) |
Yes I did, and I can confirm it works very well. |
Oh, and the crontab you create within the script indicates /etc/pi_rsynch.sh ; I edited it as it should be /etc/pihole/pi_rsynch.sh :-) |
I made the changes but I am unable to test it properly, but I did as you suggested and I think it will work just as before and is now better optimized |
Made changes, please tell me if you find more optimizations! |
I was wondering if we really needed the
pihole -g
command?As we rsync the whole DB, I think that a simple stop / restart / reload list would be enough, or am I wrong?
Other than that, your script is simple and do all I need. Thanks for that :-)
The text was updated successfully, but these errors were encountered: