71f5a7759b
systemd conventions specify that timers trigger services with the same name (this can be overridden, of course). We're currently providing: * offlineimap-oneshot.service * offlineimap.service * offlineimap.timer This is rather confusing, since the timer doesn't actually provide the service of the same name (even though they're bundled together!!), but a different one. Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net> |
||
|---|---|---|
| .. | ||
| offlineimap-oneshot.service | ||
| offlineimap-oneshot.timer | ||
| offlineimap-oneshot@.service | ||
| offlineimap-oneshot@.timer | ||
| offlineimap.service | ||
| offlineimap@.service | ||
| README.md | ||
| layout | title | author | date | contributors | updated |
|---|---|---|---|---|---|
| page | Integrating OfflineIMAP into systemd | Ben Boeckel | 2015-03-22 | Abdo Roig-Maranges, benutzer193 | 2017-06-01 |
Systemd units
These unit files are meant to be used in the user session. You may drop them
into /etc/systemd/user or ${XDG_DATA_HOME}/systemd/user followed by
systemctl --user daemon-reload to have systemd aware of the unit files.
These files are meant to be triggered either manually using systemctl --user start offlineimap.service or by enabling the timer unit using systemctl --user enable offlineimap.timer. Additionally, specific accounts may be triggered by
using offlineimap@myaccount.timer or offlineimap@myaccount.service.
If the defaults provided by these units doesn't suit your setup, any of the
values may be overridden by using systemctl --user edit offlineimap.service.
This'll prevent having to copy-and-edit the original file.