Maybe somebody noticed that I pushed out two versions in the past couple days; ultimately functionality is still the same:
The script works. Auto-update on file changes in ~/.config/hosts-block does not.
If you happened to already install yesterday’s update (hosts-block-0.0.7+master.20250310132218.34fbc13) and have now updated to the latest (hosts-block-0.0.7+master.20250312083221.f8ce95f) you might want to check if rpm disabled hosts-block-watch-config.service. It does no harm but will, in some cases, produce extra CPU cycles.
Details
I first tried to implement file change monitoring with systemd .path units, and they are what broke the package. Starting them manually worked fine, but starting them during system init broke the bootup process.
Many reboots & tests later I’m still not 100% sure why; I enabled persistent journaling but it seems this breakage did not produce any log output whatsoever.
Now I’m trying to implement file change monitoring with inotify-tools (new dependency, thanks nephros) but that, too, carries lots of pitfalls (not of the bricking kind though).