CondorCORE/condorcore-keyring
CondorCORE/condorcore-keyring
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

restart wkd sync on failure...

Browse Source 
... but with a reasonable delay of five minutes, and limited to three
invocations per hour. After that the service goes into failed state.

This should mitigate service failure caused by intermittent network
issues or server reboot on our side.
This commit is contained in:
Christian Hesse 2022-11-28 10:47:16 +01:00
parent 594009f981
commit 1c296bf292
No known key found for this signature in database
GPG Key ID: 6D42BDD116E0068F
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
wkd_sync/archlinux-keyring-wkd-sync.service.in
View File

@ -5,9 +5,13 @@ ConditionPathIsReadWrite=/etc/pacman.d/gnupg/
ConditionFileIsExecutable=SCRIPT_TARGET_DIR/archlinux-keyring-wkd-sync ConditionFileIsExecutable=SCRIPT_TARGET_DIR/archlinux-keyring-wkd-sync
Description=Refresh existing keys of archlinux-keyring Description=Refresh existing keys of archlinux-keyring
Wants=network-online.target Wants=network-online.target
StartLimitIntervalSec=1hour
StartLimitBurst=3
[Service] [Service]
ExecStart=SCRIPT_TARGET_DIR/archlinux-keyring-wkd-sync ExecStart=SCRIPT_TARGET_DIR/archlinux-keyring-wkd-sync
Restart=on-failure
RestartSec=5minutes
CapabilityBoundingSet= CapabilityBoundingSet=
DeviceAllow= DeviceAllow=