Page MenuHome GnuPG

Use exponential backoff when spawning agent and dirmngr
Closed, ResolvedPublic


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.

Event Timeline

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).

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 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 claimed this task.

Hard to test without instrumenting the code.