Cron Jobs


Ich bin mit dem Pi-hole nach langem testen endlich auf dem endgültigem Sstem angekommen. Pi-Hole läuft jetzt bei mir auf einem NUC5 mit Debian 9.

Nun möchte ich die automatischen Updates einrichten, komme jedoch nicht weiter…

Inhalt der /etc/cron.d/pihole - Update und Flush ausgeschaltet:

# Pi-hole: A black hole for Internet advertisements
# (c) 2017 Pi-hole, LLC (
# Network-wide ad blocking via your own hardware.
# Updates ad sources every week
# This file is copyright under the latest version of the EUPL.
# Please see LICENSE file for your rights under this license.
# This file is under source-control of the Pi-hole installation and update
# scripts, any changes made to this file will be overwritten when the softare
# is updated or re-installed. Please make any changes to the appropriate crontab
# or other cron file snippets.

# Pi-hole: Update the ad sources once a week on Sunday at a random time in the
#          early morning. Download any updates from the adlists
# 9 3   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity

# Pi-hole: Flush the log daily at 00:00
#          The flush script will use logrotate if available
#          parameter "once": logrotate only once (default is twice)
#          parameter "quiet": don't print messages
# 00 00   * * *   root    PATH="$PATH:/usr/local/bin/" pihole flush once quiet
# @reboot root /usr/sbin/logrotate /etc/pihole/logrotate

# Pi-hole: Grab local version and branch every 10 minutes
*/10 *  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker local

# Pi-hole: Grab remote version every 24 hours
32 14  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

Richtig so?

und “Inhalt” von crontab -e um als root Pi-hole, Listen und Debian aktuell zu halten

# Edit this file to introduce tasks to be run by cron.
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# For more information see the manual pages of crontab(5) and cron(8)
# m h  dom mon dow   command
0 2 * * * pihole -g
0 1 * * 3 pihole -up
0 3 */7 * * sudo apt-get clean && sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get autoclean && sudo apt-get -y autoremove && sudo reboot now
0 4 */14 * * sudo apt-get clean && sudo apt-get update && sudo apt-get -y dist-upgrade && sudo apt-get autoclean && sudo apt-get -y autoremove && sudo reboot now

Stimmen die alle so?


Pi-Hole is already set up to update gravity weekly on Sunday morning at a time between 0300 and 0500 (0309 in your case). The random time avoids excessive server queries at once from all Pi-Hole users.

Commenting out these cron lines disables these features.

Your proposed system update cron should be in addition to the existing Pi-Hole cron script, rather than replacing the script.

This cron is not necessary. On the master branch, changes occur infrequently and are announced and would be shown as an update available on your dashboard through the existing version checks.