Date: Wed, 16 Jun 1999 13:41:40 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: junkmale@xtra.co.nz Cc: security@FreeBSD.ORG, Dag-Erling Smorgrav <des@flood.ping.uio.no> Subject: Re: named timeouts Message-ID: <10262.929533300@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 16 Jun 1999 23:27:43 %2B1200." <19990616113019.HOKO311284.mta2-rme@wocker>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <19990616113019.HOKO311284.mta2-rme@wocker>, "Dan Langille" writes: >On 16 Jun 99, at 13:17, Poul-Henning Kamp wrote: >> Actually it doesnt, it means that the client closed his socket before >> named got to answer... > >OK. Now we're back to my initial theory. How do I increase the time the >client keeps the socket open? Or is that something possible to configure? My guess is that the following happens: Client Named create socket send request-------------------> search through the entire world for answer, this takes send request------------------->quite some time, in fact very long time before we find the answer and receive answer<---------------- respond close socket handle next request (from cache) log_in_vain...<---------------- respond -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10262.929533300>