GnuPG 1.2.1 trustdb checks for every pubkey import?

[Ingo Klöcker]

--Boundary-02=_jUNY+QTdsnJuGDW
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Thursday 27 February 2003 05:11, gabriel rosenkoetter wrote:
> For reference, here's what a --check-trustdb looks like for me these
> days:
>
> uriel:~% time gpg --check-trustdb
> gpg: checking at depth 0 signed=3D46 ot(-/q/n/m/f/u)=3D0/0/0/0/0/1
> gpg: checking at depth 1 signed=3D84 ot(-/q/n/m/f/u)=3D0/0/0/17/29/0
> gpg: checking at depth 2 signed=3D288 ot(-/q/n/m/f/u)=3D0/0/0/72/7/0
> gpg: checking at depth 3 signed=3D181 ot(-/q/n/m/f/u)=3D0/74/0/22/1/0
> gpg: checking at depth 4 signed=3D0 ot(-/q/n/m/f/u)=3D0/0/0/0/1/0
> gpg: next trustdb check due at 2003-03-07
> gpg --check-trustdb  109.24s user 20.77s system 80% cpu 2:40.70 total

Try running gpg with the following undocumented parameter (it's neither=20
mentioned in the manual page nor in the --help):
gpg --rebuild-keydb-caches

It should only be necessary if one updates from GnuPG 1.0.6 (or older)=20
to GnuPG 1.0.7 (or newer).

Regards,
Ingo


--Boundary-02=_jUNY+QTdsnJuGDW
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+YNUiGnR+RTDgudgRAi6BAJ9u7y1LaU2pL6ohkgCd7afozVZuSQCfdGZ1
yAY+PRPFuzgV1OOMIpq0+nI=
=MzLG
-----END PGP SIGNATURE-----

--Boundary-02=_jUNY+QTdsnJuGDW--