From owner-freebsd-security Wed Jun 16 5:54: 7 1999 Delivered-To: freebsd-security@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C072F150B7 for ; Wed, 16 Jun 1999 05:54:02 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA10511; Wed, 16 Jun 1999 14:53:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: dan.langille@dvl-software.com, security@FreeBSD.ORG, Mike Nowlin Subject: Re: named timeouts In-reply-to: Your message of "16 Jun 1999 13:56:42 +0200." Date: Wed, 16 Jun 1999 14:53:06 +0200 Message-ID: <10509.929537586@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Dag-Erling Smorgrav writes: >> Actually it doesnt, it means that the client closed his socket before >> named got to answer... > >Doh! I inverted 'to' and 'from' in my head. Am I the only one to >expect 'from' to come before 'to'? AHA!!! You never owned a HP calculator! Clearly a math weenie with a TI style "just type it as it is written" attitude :-) -- 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