aboutsummaryrefslogtreecommitdiffstats
path: root/g10/import.c
diff options
context:
space:
mode:
authorNIIBE Yutaka <[email protected]>2019-07-01 04:07:22 +0000
committerNIIBE Yutaka <[email protected]>2019-07-01 04:13:36 +0000
commit526714806da4e50c8e683b25d76460916d58ff41 (patch)
tree846cdeaa3de673a646cf871cac493db5300e84f6 /g10/import.c
parentspelling: Fix "synchronize" (diff)
downloadgnupg-526714806da4e50c8e683b25d76460916d58ff41.tar.gz
gnupg-526714806da4e50c8e683b25d76460916d58ff41.zip
tools: gpgconf: Killing order is children-first.
* tools/gpgconf-comp.c (gc_component_kill): Reverse the order. -- Cherry-picked from master commit: 7c877f942a344e7778005840ed7f3e20ace12f4a The order matters in a corner case; On a busy machine, there was a race condition between gpg-agent's running KILLAGENT command and its accepting incoming request on the socket. If a request by gpg-connect-agent was accepted, it resulted an error by sudden shutdown. This change of the order can remove such a race. Here, we know backend=0 is none. GnuPG-bug-id: 4577 Signed-off-by: NIIBE Yutaka <[email protected]>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions