3
2
Fork
You've already forked timecheck
5

systemd (timer) unit/ system service #17

Open
opened 2020年06月16日 10:56:17 +02:00 by jonas-l · 4 comments
Contributor
Copy link

That sound better than a cronjob, yeah. But as you already mentioned not all Linux distros use systemd so maybe we should consider to keep the cronjob thing as fallback if the script notices that systemd is not installed.

So it should be something for the case that the user has systemd and otherwise it should tell the user to use a cronjob.

Another idea would be to keep this script running and to include a sleep. Then one could create a systemd service unit and it would be easy to support other service managers.

> That sound better than a cronjob, yeah. But as you already mentioned not all Linux distros use systemd so maybe we should consider to keep the cronjob thing as fallback if the script notices that systemd is not installed. So it should be something for the case that the user has systemd and otherwise it should tell the user to use a cronjob. Another idea would be to keep this script running and to include a sleep. Then one could create a systemd service unit and it would be easy to support other service managers.
Collaborator
Copy link

I think the timer option would be better than a long running script...

I think the timer option would be better than a long running script...
Collaborator
Copy link

Oh wait just noticed that a systemd timer also needs a service unit...

Oh wait just noticed that a systemd timer also needs a service unit...
Author
Contributor
Copy link

the "service" can be of the type oneshot which just runs a command and then keeps it stopped until it is started by something again

the "service" can be of the type oneshot which just runs a command and then keeps it stopped until it is started by something again
Collaborator
Copy link

Yeah I think that would probably be the best solution with cronjob as fallback for now (if the system does not have systemd installed)

Yeah I think that would probably be the best solution with cronjob as fallback for now (if the system does not have systemd installed)
Sign in to join this conversation.
No Branch/Tag specified
master
testing
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nuron/timecheck#17
Reference in a new issue
nuron/timecheck
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?