# Second level Blacklist triggered on a schedule

**URL:** <https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715>\
**Category:** Duplicate\
**Created:** [September 18, 2019, 1:45pm UTC](https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715 "2019-09-18T13:45:08Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![callumw](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/callumw/32/10002_2.png) [@callumw](https://discourse.pi-hole.net/u/callumw)\
**Post date:** [September 22, 2019, 11:13am UTC](https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715/14 "2019-09-22T11:13:41Z")

</div>

Addendum - Although the pilhole-g command does work, it's slow and puts extra strain on the main block list servers.

An alternative (and much faster) way of refreshing the lists can be done by disabling and re-enabling pihole or as @jfb suggested, a _ **pihole-FTL restart** _.

Example pihole restart cron:

```auto
0 7 * * * root pihole disable && cat /etc/pihole/regex.list.standard > /etc/pihole/regex.list && pihole enable
0 23 * * * root pihole disable && cat /etc/pihole/regex.list.extra >> /etc/pihole/regex.list && pihole enable
```

Example FTL restart cron:

```auto
0 7 * * * root cat /etc/pihole/regex.list.standard > /etc/pihole/regex.list && service pihole-FTL restart > /dev/null 2>1&
0 23 * * * root cat /etc/pihole/regex.list.extra >> /etc/pihole/regex.list && service pihole-FTL restart > /dev/null 2>1&
```

---

_[View the full topic](https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715)._