-
Notifications
You must be signed in to change notification settings - Fork 17
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.
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
Use systemd timers instead of cron #48
Comments
See also digitalocean/do-agent#266 |
Thanks for bringing this to our attention @QuLogic ! I'll discuss it with my team and get back here with any updates. |
I would like to support this proposal as well. |
RosstheRoss
added a commit
to RosstheRoss/droplet-agent
that referenced
this issue
Sep 24, 2024
Allows users to use their choice of cron implementation (eg. systemd-cron). A workaround for digitalocean#48 Signed-off-by: Matt Strapp <[email protected]>
QuLogic
changed the title
Use systemd timers insteaad of cron
Use systemd timers instead of cron
Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The droplet agent package requires cron, and installs files in
/etc/cron.*
but I otherwise have no other need for cron. Since the packaging instructions say systemd is the preferred form of management, this should apply to the maintenance jobs as well. Stuff like this random delay can be specified directly in the timer unit instead of written manually.Describe the solution you'd like
Provide systemd timer unit files, and change the packaging to not depend on cron.
The text was updated successfully, but these errors were encountered: