pi-hole/advanced/Scripts
Adam Warner 340b37ab51
Stop double-rotating logs now that pihole is in /etc/logrotate.d
Our config moved into /etc/logrotate.d/pihole a while back, so the
system's own scheduled logrotate now picks it up too. Our nightly and
@reboot forced runs were still using a private state file though, so
the system's run and ours each rotated the same logs independently,
unaware of each other.

Drop the private state file and use logrotate's default one instead,
so both sides agree on what's already been rotated. Also clean up the
now-stale /etc/pihole/logrotate and private state file left behind by
older installs.

Signed-off-by: Adam Warner <me@adamwarner.co.uk>
2026-07-07 13:40:38 +01:00
..
database_migration Rename views, upgrade gravity database and bump gravity databae version 2025-08-15 19:39:21 +02:00
api.sh Revert "pihole api - use keepalive for curl queries" 2025-07-26 12:35:02 +01:00
COL_TABLE Set color codes when FORCE_COLOR is true 2025-06-24 19:03:24 +02:00
list.sh Remove readonly from list.sh to avoid errors 2025-07-14 21:20:39 -03:00
piholeCheckout.sh Prevent exiting due to set -e 2026-03-22 10:01:11 +01:00
piholeDebug.sh Use /etc/logrotate.d/pihole for logrotate file instead of /etc/pihole/logrotate 2026-05-13 08:38:31 +02:00
piholeLogFlush.sh Stop double-rotating logs now that pihole is in /etc/logrotate.d 2026-07-07 13:40:38 +01:00
piholeNetworkFlush.sh Remove readonly from piholeNetworkFlush.sh to avoid error message 2026-03-01 17:29:19 -03:00
query.sh Update advanced/Scripts/query.sh 2025-07-12 22:25:22 +00:00
update.sh update: abort if FTL branch does not exist 2025-07-10 21:37:28 +02:00
updatecheck.sh Apply suggestions from code review 2026-04-17 17:13:01 +02:00
utils.sh We can also hardcode the PID file location in utils.sh 2026-04-25 10:51:55 +01:00
version.sh Set versions in /etc/pihole/versions to null if script fails 2026-04-17 17:13:01 +02:00