Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

systemctl example #36

Open
ziggie216 opened this issue Oct 25, 2021 · 2 comments
Open

systemctl example #36

ziggie216 opened this issue Oct 25, 2021 · 2 comments

Comments

@ziggie216
Copy link

ziggie216 commented Oct 25, 2021 •
edited
Loading

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
@mtijas
Copy link

mtijas commented Dec 17, 2021 •
edited
Loading

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.

@mooleshacat
Copy link

mooleshacat commented Jan 3, 2022 •
edited
Loading

Yes it should be, I found out before seeing this and made a PR #38

You can also under [service] add:

User=root
Group=root

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ziggie216 @mtijas @mooleshacat