Re: [Sks-devel] Screen corruption on current CVS (op=index)

[Yaron M. Minsky]

That's not necessarily a sign of going banannas.  If, for instance, the
machine in question just got access to a large number of new keys.  That
would put it in a position where it doesn't know if your copies or its
copies are more up-to-date, and so would re-request lots of keys from
you.

Not sure if that's what happened, of course.

On Tue, 2004-02-24 at 00:33, Fabio Massimo Di Nitto wrote:
> Hi Olaf,
> 
> On Mon, 23 Feb 2004, Olaf Gellert wrote:
> 
> > Hm? It could be that something is still missing (for
> > example the photo-id) ;-)
> > But I am syncing with our own hkp (blackhole.pca.dfn.de)
> > and a bunch of SKS servers:
> >
> > http://pgpkeys.pca.dfn.de/pks/lookup?op=stats
> 
> I think your sks is going banana once in a while. Yesterday you requested
> more than 89000 keys from my server. Can you kindly take a look to it?
> 
> 2876 -rw-r--r--    1 debian-sks debian-sks  2937957 Feb 24 05:36 
> diff-193.174.13.74.txt
> 
> wc -l diff-193.174.13.74.txt
> 89029 diff-193.174.13.74.txt
> 
> Thanks
> Fabio
-- 
|--------/            Yaron M. Minsky              \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|

Open PGP --- KeyID B1FFD916
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916