[RC5] The recent crash.

Seth Dillingham seth at snet.net
Tue Jun 23 19:14:29 EDT 1998

The master keyserver could just be written to only accept a certain 
number of connections at one time. That's much easier than making the 
proxies cooperate when the master keyserver can't be reached.

While I think that *some* limit like this is probably a good idea, 
upgrading the key server is a good idea too. As d.net grows, it will 
naturally outgrow its equipment. The right answer isn't always "throwing 
money at it" or "installing new iron", but sometimes that *is* the right 

Hmm. I wonder if anybody remembers me... sure has been a long time since 
I said anything around here. ;-)


On 6/23/98 3:58 AM, simon at geordie.demon.co.uk (simon at geordie.demon.co.uk) 

>2) This is probably a bit harder to code. If a proxi can't find the
>master, it should then try and contact other proxies. If it can find most
>of them, and the other proxies also can't find the keyserver, then they
>shoudl agree between them selves what order they should return their
>blocks in when the keyserver comes back on line.  I.E. if there are 20
>proxies, and they can't find the key server then they should agree between
>them selves that each proxy should only try and contact the master for say
>5 mins every houre ? Or they could agree a long enough slot to enable them
>to flush their blocks. 
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest

More information about the rc5 mailing list