t; next check is scheduled for e.g. 31-12-2002:
>
> gpg: checking the trustdb
> [...]
> gpg: next trustdb check due at 2002-12-31
>
> And then, the next day, or half a week later, it does it all over
> again? Is it lying?
I think gpg tries to implicitly figure out when the tru
also sprach Tom Cook <[EMAIL PROTECTED]> [2002.10.10.1144 +0200]:
> And your system clock is not being reset every day or so?
My system clock is flakey, but the delta never exceeds the 3-7 seconds
range.
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*
hat the
> next check is scheduled for e.g. 31-12-2002:
>
> gpg: checking the trustdb
> [...]
> gpg: next trustdb check due at 2002-12-31
>
> And then, the next day, or half a week later, it does it all over
> again? Is it lying?
And your system clock is not being reset
ii gnupg 1.2.0-1GNU privacy guard - a free PGP replacement.
It happens very often that GPG decides to check the trustdb. When it's
*f-i-n-a-l-l-y* done (takes like 10 minutes or so), it says that the
next check is scheduled for e.g. 31-12-2002:
gpg: checking the tr
4 matches
Mail list logo
