Yea, as I was playing around with it the service file only writes 127.0.0.1(?) to resolv.conf. Why or how any other nameservers are in there is beyond me. But it has been working fine here.

But I agree, we can just comment (or patch) out the related lines, that is if we don't want to add openresolv as a dependency. I could set the SlackBuild up to check and patch them out if /usr/sbin/resolvconf is not found.

Otherwise I have been testing using the service file with openresolv and it has been working normal. The only issue that I ran into is if you check /var/log/pihole-FTL.log you will see that it tries to create /run/pihole-FTL.pid and /run/pihole-FTL.port, then complains about something. BUT the default config is set up to use /var/run/pihole-FTL.pid, etc.

This app is starting to feel a little half-baked to me.

Edit:
I did have to adjust the path in the service file for resolvconf from /sbin/resolvconf to /usr/sbin/resolvconf

Well if everything has been going well with pi-hole for everyone, I am going to finalize it.

It seems that even though it tries to create /run/pihole-FTL.{pid,port} it doesn't matter because /var/run/pihole-FTL.{pid,port} are created and used.

SO, I am going to add openresolv as a dependency, add the service file as rc.pihole-FTL, add info about how to start it at boot time and edit the uid/gid to something more reasonable, that is also not already accounted for at SBo.

Finally, I am going to move them from GitHub to my NotABug HackBuild repo. (link in sig)

I am/have targeted this for current (15) but if needed, php-7.1 for 14.2 is here thanks to volkerdi. Remember that you will need the alpine SlackBuild/source from 14.2 along side of php so it builds correctly. And you should also fix mod_php as explained here.

I expect to have this all done within a few days, next weekend at the latest.

I also would like to put your names somewhere in the SlackBuilds (SavoTU and PROBLEMCHYLD), so any thoughts about that?

1 members found this post helpful.

Cool, I'm still around just been busy until the next holidays and after that it's all work from there. I just dug out another old laptop to do some testing. It's a Toshiba, I'll list the specs tomorrow. Thanks for your hard work and dedication.

1 members found this post helpful.

Here are the specs, https://support.dynabook.com/support...mTOCLink=false

I'm pretty sure its standard because I haven't change anything since back in the day. It's been in the closet for about 3 1/2 years. I might soup it since Intel can't get their schit together. I've never been an AMD fanboy, but since Intel is losing ATM, I don't have much of a choice. This will be my test bed.

Yea, I am also on the dump Intel bandwagon.

But those specs make me think that I have a C640 and a D410 sitting in the closet just collecting dust. Maybe I can salvage one of them into a pi-hole.

I have made some more (minor) updates to the pi-hole SlackBuilds, but it wont be until later tonight that I can upload them. The testrig is running a test build right now.

1 members found this post helpful.

The next few days, I'm gonna be extremely busy, but this weekend I'll have time to test. Either way, I'll report my findings. Thanks again.............!!!!!!!!!!!!!!!!!

1 members found this post helpful.

Well, it's done?

rc.pihole-FTL has been created and openresolv has been added as a dependency.

The UID/GID has been set to 500 unless someone from SBo wants to reserve something different.

I have added another option CRON=no/yes, (default is no) to add a cron file in /etc/cron.d that should update the adlists weekly and flush the daily log. This should be considered "testing", as I have not tested it yet. The adlist job should create a log '/var/log/pihole_updateGravity.log', make sure to check if it is working correctly. Otherwise, you can set your own cron jobs via crontab.

I will try to submit it to SBo once Slackware 15 is released, but IDK it just seems a bit "hacky". If they don't want it there, I'll keep it in my HackBuilds. If they do accept it, the UID/GID will likely change again.

Next, I am going to tread in dangerous waters and start setting up my pi-hole server. I think that I successfully had a static IP working on my testrig when I had it wired in so I think that I'll be ok.

If I get time before the weekend I'll test, if not I'll report back and during the weekend. Thanks again....

1 members found this post helpful.

Will you be revising the slackbuild on github?

Updates? I will once it is in my HackBuilds repo. It's not easy for me to maintain my GitHub repos. I keep all that on a different PC and it gets wiped out regularly. And, I don't particularly like GitHub.

Otherwise I think that it is ready. Is there something that needs to be fixed?

No, I don't think so. I'll report later. Got the system ready to go.

Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- a/gravity.sh
|+++ b/gravity.sh
--------------------------
patching file gravity.sh
Using Plan A...
Hunk #1 succeeded at 19.
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- a/pihole
|+++ b/pihole
--------------------------
patching file pihole
Using Plan A...
Hunk #1 succeeded at 17.
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|
|--- a/advanced/Scripts/piholeDebug.sh
|+++ b/advanced/Scripts/piholeDebug.sh
--------------------------
patching file advanced/Scripts/piholeDebug.sh
Using Plan A...
Hunk #1 succeeded at 68.
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|
|--- a/advanced/Scripts/webpage.sh
|+++ b/advanced/Scripts/webpage.sh
--------------------------
patching file advanced/Scripts/webpage.sh
Using Plan A...
Hunk #1 succeeded at 16.
Hmm... Ignoring the trailing garbage.
done
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -uprN pi-hole-4.3.2/advanced/Scripts/version.sh pi-hole-4.3.2.cust/advanced/Scripts/version.sh
|--- pi-hole-4.3.2/advanced/Scripts/version.sh 2019-09-15 17:52:21.000000000 +0200
|+++ pi-hole-4.3.2.cust/advanced/Scripts/version.sh 2019-09-24 17:39:11.828971157 +0200
--------------------------
patching file advanced/Scripts/version.sh
Using Plan A...
Hunk #1 succeeded at 20.
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -uprN pi-hole-4.3.2/pihole pi-hole-4.3.2.cust/pihole
|--- pi-hole-4.3.2/pihole 2019-09-15 17:52:21.000000000 +0200
|+++ pi-hole-4.3.2.cust/pihole 2019-09-24 17:39:11.786971218 +0200
--------------------------
patching file pihole
Using Plan A...
Hunk #1 succeeded at 57.
Hunk #2 succeeded at 75.
Hunk #3 succeeded at 300.
Hunk #4 succeeded at 322.
Hunk #5 succeeded at 335.
Hunk #6 succeeded at 374.
Hmm... Ignoring the trailing garbage.
done
Hmm... Looks like a unified diff to me...
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -uprN AdminLTE-4.3.2/scripts/pi-hole/php/footer.php AdminLTE-4.3.2.cust/scripts/pi-hole/php/footer.php
|--- a/AdminLTE-4.3.2/scripts/pi-hole/php/footer.php 2019-09-22 01:06:20.000000000 +0200
|+++ b/AdminLTE-4.3.2/scripts/pi-hole/php/footer.php 2019-09-24 17:39:11.836971145 +0200
--------------------------
File to patch:

It hangs at compile.

Ooops. Yea that's my fault, fixed.

I moved some things around and forgot that that gets extracted and patched later in the SlackBuild.

Great job!!!!!!

Attached Thumbnails

 

1 members found this post helpful.

Did you use the cron job? If so, you'll want to watch the logs and make sure that it is working correctly.