Re: client doesn't recover after server restart|
fn ln <neplace1,AT,yahoo,DOT,ca>|
Tue, 12 Feb 2002 11:40:02 +0100|
Thanks Keith !
Got your patch, I'll give it a shot ...
If I understand things correctly, this is a flaw in
the program :) Now the question is whether it flaw is
on the protocol design or on the protocol
Has anybody seriously looked into the protocol level
to see whether it's a flaw in design or in
implementation ? If the design was to be enhanced /
fixed to avoid this bug, would it inevitably break
backward compatibility with previous versions ?
I guess your patch is a workaround on the protocol
--- Keith Smith <keith,AT,ksmith,DOT,com> wrote:
> Heheheheh, ... As I was saying earlier on the list
> ... :)
> Apply my CIPE foreground patch and run out of inetd
> with maxerr set to a
> SMALL value, like 2.
> ci00:234:respawn:/usr/local/sbin/ciped-cb -f -o
> You and I have/had the same problems at some of the
> I'll mail you the patch under seperate cover.
> Takes anywhere from a few seconds to a minute or so
> to recover depending
> on the values for ping & timeout. Don't set your
> ping values too low,
> you create a lot of unneeded overhead.
> Keith Smith keith,AT,ksmith,DOT,com
> 655 W Fremont Dr
> Tempe AZ 85282 it's hot
Web-hosting solutions for home and business! http://website.yahoo.ca