Package Details: pi-hole-ftl 3.0-2

Git Clone URL: https://aur.archlinux.org/pi-hole-ftl.git (read-only)
Package Base: pi-hole-ftl
Description: The Pi-hole FTL engine
Upstream URL: https://github.com/pi-hole/FTL
Licenses: EUPL-1.1
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 13
Popularity: 1.970376
First Submitted: 2017-05-07 15:23
Last Updated: 2018-07-15 08:22

Pinned Comments

max.bra commented on 2018-02-09 16:46

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.

Latest Comments

max.bra commented on 2018-07-15 08:25

@butterymales

there's no need at all to manage /run/pihole-ftl/FTL.sock as a tmpfiles. Thanks for reporting.

butterymales commented on 2018-07-14 18:05

/run/pihole-ftl/FTL.sock is causing pacman to return an error on every package when creating temporary files:

 (3/4) Creating temporary files...
 error: command failed to execute correctly

Running systemd-hook tmpfiles returns the following:

$ sudo /usr/share/libalpm/scripts/systemd-hook tmpfiles
/run/pihole-ftl/FTL.sock is not a file.

When the FTL service is stopped (and FTL.sock is gone) pacman no longer returns errors when installing packages. Is there any way to fix this?

graysky commented on 2018-02-17 11:44

Has anyone else noticed that TIMEFRAME=today setting in /etc/pihole/pihole-FTL.conf is being ignored on this update?

max.bra commented on 2018-02-09 16:46

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.

max.bra commented on 2017-12-13 16:16

2.12-3 please refer to Pi-hole wiki for new configuration options

max.bra commented on 2017-12-13 12:34

Stop official service

pi-hole-ftl no-deamon debug

graysky commented on 2017-12-13 12:31

I can confirm that, 60, 120, and 600 work. But 3600 does not.

...how did you get that debug output?

max.bra commented on 2017-12-13 12:20

@graysky i suspected it.

I noticed yesterday that the commit countdown starts from an integer portion of time. I'll explain:

my yesterday test was on a 10-minute commit and the debug output, summarizing, said:

20:43 ftl started

20:50 commit

21:00 commit

so it may be that for portions of time greater than one hour it can not trigger.

need to inspect the source

graysky commented on 2017-12-13 12:09

Is anyone else experiencing no writes to /etc/pihole/pihole-FTL.db with large values such as 3600 (package default)?

max.bra commented on 2017-12-11 23:03

waiting for a parameterized version, you can customize the FTL database commit interval by modifying the following PKGBUILD line:

sed -i "s|#define DBinterval 60|#define DBinterval 3600|w $_ssc" "$srcdir"/$_pkgname-$pkgver/FTL.h

where 3600 is for this package new timing of an hour. you can write 600 for 10 minutes or 7200 for 2 hours and so on.

All comments