-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
offlineimap.timer doesn't work #469
Comments
Thanks @knezi, you are correct, the timer has to be initialized the first time for |
May I ask why this is required? |
Github-ref: #469 Reported-by: Jan Knížek <jk@janknizek.cz> Signed-off-by: benutzer193 <registerbn@gmail.com> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Patch applied, BTW. |
@nicolas33 because OnUnitInactiveSec specificies how many seconds after the last run next run will be executed. When you boot, there's no last run and therefore the timer won't be triggered. This is why you add OnBootSec, which will run it once after boot and then it will be run repeatedly thanks to the first parameter. |
Ok, thank you. |
If I simply activate the provided timer by:
Then
systemctl --user list-timers
lists this timer, but all times (next, past) are N/A. It works if I add this line into the timer:So I guess there needs to be specified first time of run and then the repetition.
The text was updated successfully, but these errors were encountered: