Open ziggie216 opened 2 years ago
Yes it indeed should be ExecStart=/usr/local/bin/pihole-cloudsync/pihole-cloudsync --pull
. I just set up pihole-cloudsync (seems like a great project btw!) and didn't notice the "wrong" command at first (just copied the example from the README). After fixing the ExecStart command as you described above, systemd service started working.
Edit: That second pihole-cloudsync
is needed because the repository gets cloned inside the pihole-cloudsync
directory at first.
Came here to report this issue and saw it's already reported, so just commenting/confirming this here.
Yes it should be, I found out before seeing this and made a PR https://github.com/stevejenkins/pihole-cloudsync/pull/38
You can also under [service] add:
User=root
Group=root
For the README.me, Automating with systemd, systemd Details, .service its show this line ExecStart=/usr/local/bin/pihole-cloudsync --pull
shouldn't it be? ExecStart=/usr/local/bin/pihole-cloudsync/pihole-cloudsync --pull