how about 10 mins? it seems to be a good timings. comunity?
Search Criteria
Package Details: pi-hole-ftl 6.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/pi-hole-ftl.git (read-only, click to copy) |
|---|---|
| Package Base: | pi-hole-ftl |
| Description: | The Pi-hole FTL engine |
| Upstream URL: | https://github.com/pi-hole/FTL |
| Licenses: | EUPL-1.2 |
| Conflicts: | dnsmasq |
| Provides: | dnsmasq |
| Submitter: | max.bra |
| Maintainer: | max.bra (graysky) |
| Last Packager: | max.bra |
| Votes: | 59 |
| Popularity: | 0.86 |
| First Submitted: | 2017-05-07 15:23 (UTC) |
| Last Updated: | 2025-03-30 17:00 (UTC) |
Dependencies (6)
- gmp (gmp-hgAUR)
- mbedtls (mbedtls-gitAUR, mbedtls-dtlsAUR)
- nettle (nettle-gitAUR)
- pi-hole-webAUR
- cmake (cmake-gitAUR, cmake3AUR) (make)
- xxd (vim-minimal-gitAUR, gvim-gitAUR, vim-cli-gitAUR, gvim-wayland-lilydjwg-gitAUR, gvim-gtk2AUR, gvim, tinyxxd, vim) (make)
Required by (66)
- adhocspot-script-git (requires dnsmasq)
- airgeddon (requires dnsmasq) (optional)
- anti-ad-dnsmasq-git (requires dnsmasq)
- appgate-sdp (requires dnsmasq) (optional)
- appgate-sdp-headless (requires dnsmasq) (optional)
- archpxe (requires dnsmasq)
- berate_ap-git (requires dnsmasq)
- blueman-git (requires dnsmasq) (optional)
- corplink-bin (requires dnsmasq)
- create_ap (requires dnsmasq)
- create_ap-git (requires dnsmasq)
- cuttlefish-base-git (requires dnsmasq)
- dns-zone-blacklist-git (requires dnsmasq) (optional)
- dnsmasq-china-list-git (requires dnsmasq)
- dnsmasq-openrc (requires dnsmasq)
- docker-dnsmasq (requires dnsmasq)
- docker-machine-driver-kvm2 (requires dnsmasq)
- easywifi-git (requires dnsmasq) (optional)
- ethoscope-device (requires dnsmasq)
- ethoscope-node (requires dnsmasq)
- Show 46 more...
Sources (5)
max.bra commented on 2017-12-11 22:26 (UTC)
max.bra commented on 2017-12-11 22:25 (UTC)
I had not seen that define: problem solved!
graysky commented on 2017-12-11 22:20 (UTC)
@max - DL6ER replied to my upstream ticket. Perhaps we can use a longer default as a trade-off? Problem is doing it is modifying upstream's default on the package-level (although we do this extensively anyway with the logs to tmpfs which I totally agree with!
Here is a patch changing it from every 1 min to every 10 min (although you should just use your sed construct in the prepare function too):
--- a/FTL-2.12/FTL.h 2017-12-06 22:35:44.000000000 -0500
+++ b/FTL-2.12/FTL.h 2017-12-11 17:15:47.145632801 -0500
@@ -68,7 +68,7 @@
// How often do we dump into FTL's database?
// Default: 60 (once per minute)
-#define DBinterval 60
+#define DBinterval 600
// Static structs
typedef struct {
max.bra commented on 2017-12-11 21:33 (UTC)
@graysky yes yes, minute not second... my fault!
graysky commented on 2017-12-11 21:29 (UTC)
@max.bra - Are you sure it's once per second and note once per minute? I opened https://github.com/pi-hole/pi-hole/issues/1839
max.bra commented on 2017-12-11 21:21 (UTC) (edited on 2017-12-11 21:33 (UTC) by max.bra)
yes, a 1 minute commit time. confirmed!! gasp!!
max.bra commented on 2017-12-11 21:20 (UTC)
ok I'm starting to write the skeleton of systemd services for the various syncs. once published we will all refine and improve them. in the meantime, I set up the server package for permissions in the /etc/pihole directory and the patch reported by MartB
graysky commented on 2017-12-11 21:15 (UTC)
@max.bra - Since /etc/pihole/pihole-FTL.db seems to be a binary file, I am going to speculate the ENTIRE file is overwritten at the 60/hour rate. So that could be 10s of MBs of writes each hour which will shorten the life of an SD Card for sure. I agree that is it a very poor design for SD cards.
max.bra commented on 2017-12-11 21:13 (UTC)
what a can't understand is how pihole guys can leave/project a so high commit rate on a raspi. I'm inclined to think of a bug...
Pinned Comments
max.bra commented on 2018-02-09 16:46 (UTC) (edited on 2019-10-18 23:13 (UTC) by max.bra)
ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.
First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.