force tuwunel's start limit off over the upstream value
This commit is contained in:
parent
c4924d227b
commit
04f8683f99
1 changed files with 4 additions and 3 deletions
|
|
@ -1048,9 +1048,10 @@ in
|
||||||
# without the registration.
|
# without the registration.
|
||||||
++ lib.optional ctlActive "${swarmAppserviceCredentialId}:${swarmAppserviceRuntimeDir}/swarm.yaml";
|
++ lib.optional ctlActive "${swarmAppserviceCredentialId}:${swarmAppserviceRuntimeDir}/swarm.yaml";
|
||||||
|
|
||||||
# Upstream's `Restart=on-failure` retries a start that failed for
|
# Upstream retries with `Restart=on-failure` every 10 s under a start
|
||||||
# want of the registration; a start limit would end the retries.
|
# limit of 5 in 60 s, which would end the retries for want of the
|
||||||
systemd.services.tuwunel.startLimitIntervalSec = lib.mkIf ctlActive 0;
|
# registration.
|
||||||
|
systemd.services.tuwunel.startLimitIntervalSec = lib.mkIf ctlActive (lib.mkForce 0);
|
||||||
|
|
||||||
# The swarm registration, fetched from the store and rendered onto
|
# The swarm registration, fetched from the store and rendered onto
|
||||||
# the tmpfs before the homeserver loads it. A store that does not
|
# the tmpfs before the homeserver loads it. A store that does not
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue