e7a3fd55ac
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>
993 B
993 B
| 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.