Mailing List Archive: GnuPG: devel

gpg-agent seems to be talking to itself a lot

Index | Next | Previous | View Threaded

hans at guardianproject

Mar 1, 2012, 2:42 PM

Post #1 of 2 (202 views)
Permalink

gpg-agent seems to be talking to itself a lot

I'm in the process of trying to get the whole gnupg 2.1 suite working on
Android now I have everything built and deployed. I can do quite a few
actions, but not all. I can go "gpg2 --import", "gpg2 --list-keys",
"gpg2 --fingerprint", and things like that.

In the process of debugging the whole setup, I noticed that gpg-agent
seems to be spending a fair amount of time talking to itself. Here's a
snippet of the log, note the timestamps:

2012-03-01 20:52:37 gpg-agent[1482] handler 0x523d0 for fd 7 started
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_7 -> OK Pleased to meet
you, process 1482
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_5 <- OK Pleased to meet
you, process 1482
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_5 -> GETINFO pid
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_7 <- GETINFO pid
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_7 -> D 1482
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_5 <- D 1482
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_7 -> OK
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_5 <- OK
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_5 -> BYE
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_7 <- BYE
2012-03-01 20:52:37 gpg-agent[1482] DBG: chan_7 -> OK closing connection
2012-03-01 20:52:37 gpg-agent[1482] handler 0x523d0 for fd 7 terminated
2012-03-01 20:53:37 gpg-agent[1482] handler 0x523d0 for fd 7 started
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_7 -> OK Pleased to meet
you, process 1482
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_5 <- OK Pleased to meet
you, process 1482
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_5 -> GETINFO pid
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_7 <- GETINFO pid
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_7 -> D 1482
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_5 <- D 1482
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_7 -> OK
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_5 <- OK
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_5 -> BYE
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_7 <- BYE
2012-03-01 20:53:37 gpg-agent[1482] DBG: chan_7 -> OK closing connection
2012-03-01 20:53:37 gpg-agent[1482] handler 0x523d0 for fd 7 terminated
2012-03-01 20:54:37 gpg-agent[1482] handler 0x523d0 for fd 7 started
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_7 -> OK Pleased to meet
you, process 1482
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_5 <- OK Pleased to meet
you, process 1482
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_5 -> GETINFO pid
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_7 <- GETINFO pid
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_7 -> D 1482
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_5 <- D 1482
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_7 -> OK
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_5 <- OK
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_5 -> BYE
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_7 <- BYE
2012-03-01 20:54:37 gpg-agent[1482] DBG: chan_7 -> OK closing connection
2012-03-01 20:54:37 gpg-agent[1482] handler 0x523d0 for fd 7 terminated

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

Mar 3, 2012, 2:15 AM

Post #2 of 2 (171 views)
Permalink

Re: gpg-agent seems to be talking to itself a lot [In reply to]

On Thu, 1 Mar 2012 23:42, hans [at] guardianproject said:
> I'm in the process of trying to get the whole gnupg 2.1 suite working on
> Android now I have everything built and deployed. I can do quite a few
> actions, but not all. I can go "gpg2 --import", "gpg2 --list-keys",
> "gpg2 --fingerprint", and things like that.

Great.

> In the process of debugging the whole setup, I noticed that gpg-agent
> seems to be spending a fair amount of time talking to itself. Here's a

Not really, it is only once a minute:

/* The timer tick used for housekeeping stuff. For Windows we use a
longer period as the SetWaitableTimer seems to signal earlier than
the 2 seconds. CHECK_OWN_SOCKET_INTERVAL defines how often we
check our own socket in standard socket mode. If that value is 0
we don't check at all. All values are in seconds. */
#if defined(HAVE_W32CE_SYSTEM)
# define TIMERTICK_INTERVAL (60)
# define CHECK_OWN_SOCKET_INTERVAL (0) /* Never */
#elif defined(HAVE_W32_SYSTEM)
# define TIMERTICK_INTERVAL (4)
# define CHECK_OWN_SOCKET_INTERVAL (60)
#else
# define TIMERTICK_INTERVAL (2)
# define CHECK_OWN_SOCKET_INTERVAL (60)
#endif

For CE we disabled it completey because we are sure that we won´t suffer
from race conditions. Those may lead on desktop to two agents
processes. Two processes don´t harm but it is better to kill the unused
one,

Shalom-Salam,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads