docker-offlineimap/contrib/systemd/offlineimap@.timer

[Unit]
Description=Offlineimap Query Timer for account %i

[Timer]
OnBootSec=1m
OnUnitInactiveSec=15m
Unit=offlineimap-oneshot@%i.service

[Install]
WantedBy=default.target
contrib: add systemd configuration files Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net> 2015-03-22 12:58:56 +01:00			`[Unit]`
			`Description=Offlineimap Query Timer for account %i`

			`[Timer]`
Fix systemd.timer: initialize timer after boot Github-ref: https://github.com/OfflineIMAP/offlineimap/issues/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> 2017-05-20 21:48:23 +02:00			`OnBootSec=1m`
contrib: add systemd configuration files Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net> 2015-03-22 12:58:56 +01:00			`OnUnitInactiveSec=15m`
Use oneshot services for systemd timers Signed-off-by: benutzer193 <registerbn@gmail.com> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net> 2017-03-28 08:20:16 +02:00			`Unit=offlineimap-oneshot@%i.service`
contrib: add systemd configuration files Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net> 2015-03-22 12:58:56 +01:00
			`[Install]`
Use a pre-existing target for systemd services Providing mail.target is really confusing and poor UX: * When a user enables a unit, it's not truly enabled until they ALSO enable mail.target. This is very counter-intuitive. * `mail.target` provides no extra value in itself, nor is it anything "standard". * Any user wanting this specific target can still continue using it just dropping in a `mail.target` file. Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net> 2017-06-01 18:14:10 +02:00			`WantedBy=default.target`