From owner-freebsd-hackers Mon Aug 17 09:27:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23495 for freebsd-hackers-outgoing; Mon, 17 Aug 1998 09:27:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23490 for ; Mon, 17 Aug 1998 09:27:24 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id OAA04944; Mon, 17 Aug 1998 14:37:19 GMT (envelope-from didier@omnix.net) Date: Mon, 17 Aug 1998 16:37:19 +0200 (CEST) From: Didier Derny To: David Greenman cc: hackers@FreeBSD.ORG, support@yard.de Subject: Re: Yard/FreeBSD Problem (fwd) In-Reply-To: <199808171348.GAA19588@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Aug 1998, David Greenman wrote: > For the server, "s" above appears to be the unconnected (listen) socket. > The TCP_NODELAY option is not propagated across to accept()ed sockets, so > you must do the setsockopt on those, not on the listen socket. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > They have made the modification on their program to do the setsockopt on the connect socket but without any success; Is there any possibily to track this socketoption to understand why it diseappear ? When I force the nodelay in the kernel everything works fine -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message