Skip to content

Commit 89bfc60

Browse files
authored
Merge pull request #1160 from pi-hole/dependabot/github_actions/master/github_action-dependencies-637f40baaf
Bump actions/stale from 9.0.0 to 9.1.0 in the github_action-dependencies group
2 parents d03b0a0 + 02af04b commit 89bfc60

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

.github/workflows/stale_pr.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ jobs:
1717
pull-requests: write
1818

1919
steps:
20-
- uses: actions/stale@v9.0.0
20+
- uses: actions/stale@v9.1.0
2121
with:
2222
repo-token: ${{ secrets.GITHUB_TOKEN }}
2323
# Do not automatically mark PR/issue as stale

docs/ftldns/cache_dump.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ sudo killall -USR1 pihole-FTL
99
Such a cache dump looks like
1010

1111
``` plain
12-
cache size 10000, 0/20984 cache insertions re-used unexpired cache entries.
12+
cache size 10000, 0/20984 cache insertions reused unexpired cache entries.
1313
queries forwarded 10247, queries answered locally 14713
1414
queries for authoritative zones 0
1515
pool memory in use 22272, max 24048, allocated 480000
@@ -80,7 +80,7 @@ where we stripped lines like `Dec 15 20:32:02 dnsmasq[4177892]:` for the sake of
8080
### Cache metrics
8181

8282
``` plain
83-
cache size 10000, 0/20984 cache insertions re-used unexpired cache entries.
83+
cache size 10000, 0/20984 cache insertions reused unexpired cache entries.
8484
```
8585

8686
tells us that the cache size is 10000 (Pi-hole's default value). None of the 20984 cache insertions had to overwrite still valid cache lines. If this number is zero, your cache was sufficiently large at any time. If this number is notably larger than zero, you should consider increasing the cache size.

0 commit comments

Comments
 (0)