gabriel rosenkoetter on Thu, 27 Feb 2003 22:01:07 -0500


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] GnuPG 1.2.1 trustdb checks for every pubkey import?


On Thu, Feb 27, 2003 at 12:47:24PM -0500, gabriel rosenkoetter wrote:
> I'm going to restart the rebuild having removed auto-key-retrieve
> from my .gnupg/gpg.conf's keyserver-options.

Round 2.

uriel:~% time gpg --no-sig-cache --rebuild-keydb-caches
gpg: checking keyring `/home/gr/.gnupg/pubring.gpg'
gpg: 50 keys so far checked (1504 signatures)
[clip]
gpg: 1429 keys checked (48777 signatures)
gpg --no-sig-cache --rebuild-keydb-caches  10367.51s user 2360.50s system 83% cpu 4:13:30.89 total
uriel:~% time gpg --check-trustdb
gpg: checking at depth 0 signed=46 ot(-/q/n/m/f/u)=0/0/0/0/0/1
gpg: checking at depth 1 signed=84 ot(-/q/n/m/f/u)=0/0/0/17/29/0
gpg: checking at depth 2 signed=288 ot(-/q/n/m/f/u)=0/0/0/72/7/0
gpg: checking at depth 3 signed=181 ot(-/q/n/m/f/u)=0/74/0/22/1/0
gpg: checking at depth 4 signed=0 ot(-/q/n/m/f/u)=0/0/0/0/1/0
gpg: next trustdb check due at 2003-03-07
gpg --check-trustdb  15.63s user 7.73s system 71% cpu 32.779 total

So I'm certainly faster than the 2m40s I was seeing before, but I'm
significantly slower per-signature than Walt is (drastically
different machines, and gcc's math output isn't so hot on mine), and
the --no-sig-cache rebuild only bought me about 4s over a regular
rebuild.

Perhaps I'll have to give in and do my trustdb checks from cron. At
least I trust my sysadmin (me!), so leaving my .gnupg on a system
liable to be active in the wee hours isn't that big a deal.

::sigh::

-- 
gabriel rosenkoetter
gr@eclipsed.net

Attachment: pgpE92ktg42MH.pgp
Description: PGP signature