pi-hole/docs
1
0
Fork 0
mirror of https://github.com/pi-hole/docs.git synced 2024-12-06 19:27:12 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Merge pull request #313 from MichaIng/patch-1

Browse Source 
Consequently use /run/pihole* for runtime files
This commit is contained in:
DL6ER
2020-08-31 21:00:03 +02:00
committed by GitHub
parent bbc756491f 25109df616
commit e96d433416
3 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ftldns/configfile.md
+3 -3
View File
@@ -123,15 +123,15 @@ Specify the path and filename of FTL's SQLite3 long-term database. Setting this
The location of FTL's log file. If you want to move the log file to a different place, also consider [this FAQ article](https://discourse.pi-hole.net/t/moving-the-pi-hole-log-to-another-location-device/2041).
#### `PIDFILE=/var/run/pihole-FTL.pid` {#file_PIDFILE data-toc-label='Process identifier file'}
#### `PIDFILE=/run/pihole-FTL.pid` {#file_PIDFILE data-toc-label='Process identifier file'}
The file which contains the PID of FTL's main process.
#### `PORTFILE=/var/run/pihole-FTL.port` {#file_PORTFILE data-toc-label='Port file'}
#### `PORTFILE=/run/pihole-FTL.port` {#file_PORTFILE data-toc-label='Port file'}
The file containing the port FTL's API is listening on.
#### `SOCKETFILE=/var/run/pihole/FTL.sock` {#file_SOCKETFILE data-toc-label='Socket file'}
#### `SOCKETFILE=/run/pihole/FTL.sock` {#file_SOCKETFILE data-toc-label='Socket file'}
The file containing the socket FTL's API is listening on.
docs/ftldns/in-depth.md
+4 -4
View File
@@ -1,6 +1,6 @@
## Available interfaces
Pi-hole stats can be accessed via a standard Unix socket (`var/run/pihole/FTL.sock`), a telnet-like connection (TCP socket on port `4711`) as well as indirectly via the Web API (`admin/api.php`), and the command line (`pihole -c -j`). You can out find more details below.
Pi-hole stats can be accessed via a standard Unix socket (`/run/pihole/FTL.sock`), a telnet-like connection (TCP socket on port `4711`) as well as indirectly via the Web API (`admin/api.php`), and the command line (`pihole -c -j`). You can out find more details below.
## Command-line arguments
@@ -19,9 +19,9 @@ Command-line arguments can be arbitrarily combined, e.g. `pihole-FTL debug test`
## File locations
- `/var/log/pihole-FTL.log` log file
- `/var/run/pihole-FTL.pid` PID file
- `/var/run/pihole-FTL.port` file containing port on which `FTL` is listening
- `/var/run/pihole/FTL.sock` Unix socket
- `/run/pihole-FTL.pid` PID file
- `/run/pihole-FTL.port` file containing port on which `FTL` is listening
- `/run/pihole/FTL.sock` Unix socket
## Linux capabilities
docs/guides/vpn/dual-VPN.md
+1 -1
View File
@@ -51,7 +51,7 @@ systemctl start openvpn@server2.service
*If your distribution does not have `systemctl` you may use the command below to start an OpenVPN daemon with your second configuration:*
```bash
/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/server2.pid --cd /etc/openvpn --config server2.conf --script-security 2
/usr/sbin/openvpn --daemon --writepid /run/openvpn/server2.pid --cd /etc/openvpn --config server2.conf --script-security 2
```
Finally, edit the existing `.ovpn` file used for the client connection. Update the port from the previous value to the port you used for the second instance of OpenVPN.