Page MenuHome GnuPG
Create Task
Maniphest T3380

Use exponential backoff when spawning agent and dirmngr
Testing, NormalPublic
Actions

Description

When spawning agent and dirmngr the gnupg should use exponential backoff when testing the spawned process for readiness. The current code makes the gnupg to wait unnecessarily long time on non-busy systems. This attached patch solves the problem.

gnupg-2.1.19-exponential.patch1 KBDownload

Revisions and Commits

rG GnuPG
rG9a3e41c151fe common: Improve lock strategy for dotlock.
rG45a1ab501787 common: Improve lock strategy for dotlock.

Related Objects

Event Timeline

t8m created this task.Sep 1 2017, 9:51 AM
t8m created this object in space S1 Public.
werner triaged this task as Normal priority.Sep 1 2017, 11:14 AM
werner edited projects, added gnupg, Feature Request; removed g10code (gnupg-2.2).
thesamesam added a subscriber: thesamesam.Sep 1 2023, 5:31 AM
werner edited projects, added gnupg24; removed gnupg.Sep 26 2023, 1:29 PM
werner added a subscriber: werner.Oct 2 2023, 1:28 PM

This was actually implemented in a similar way for T3490.

However, we also need to look at the locking code which needs a similar solution in the common case (Kleopatra) that several processes are trying to start gpg-agent. In fact there we also need some randomization of the wait time.

werner added a commit: rG45a1ab501787: common: Improve lock strategy for dotlock..Oct 2 2023, 2:41 PM
werner changed the task status from Open to Testing.Oct 2 2023, 2:41 PM
werner moved this task from Backlog to QA on the gnupg24 board.
werner added a commit: rG9a3e41c151fe: common: Improve lock strategy for dotlock..Oct 2 2023, 2:46 PM