Skip to content

Use systemd timer instead of crontab #92

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

Merged
merged 1 commit into from
Feb 18, 2020

Conversation

znz
Copy link
Member

@znz znz commented Jan 29, 2020

  • Cron's output send to mail, but systemd stores to journald.
    It can rotate logs automatically.
  • systemctl start can run jobs on same environment with running by timer.
  • Split services using by *.path.
    It is not easy to understand, but I did not discover better solution to split log and status.

- Cron's output send to mail, but systemd stores to journald.
  It can rotate logs automatically.
- `systemctl start` can run jobs on same environment with running by timer.
- Split services using by `*.path`.
  It is not easy to understand, but I did not discover better solution to split log and status.
@znz znz force-pushed the use-systemd-timer-instead-of-crontab branch from 3eb1561 to e669414 Compare January 30, 2020 03:00
@znz znz mentioned this pull request Jan 31, 2020
@znz znz merged commit e669414 into ruby:master Feb 18, 2020
@znz znz deleted the use-systemd-timer-instead-of-crontab branch February 18, 2020 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant