From owner-freebsd-net@FreeBSD.ORG Mon May 6 13:35:43 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1E180178 for ; Mon, 6 May 2013 13:35:43 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) by mx1.freebsd.org (Postfix) with ESMTP id 9A88562C for ; Mon, 6 May 2013 13:35:42 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.6/8.14.6) with ESMTP id r46DZfwL073146; Mon, 6 May 2013 17:35:41 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.6/8.14.6/Submit) id r46DZf9e073145; Mon, 6 May 2013 17:35:41 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 6 May 2013 17:35:41 +0400 From: Gleb Smirnoff To: Richard Sharpe Subject: Re: TCP_KEEPIDLE vs TCPTV_KEEP_IDLE Message-ID: <20130506133541.GB15182@glebius.int.ru> References: <20130506082235.GV15182@FreeBSD.org> <20130506132332.GZ15182@glebius.int.ru> <20130506132821.GA15182@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 13:35:43 -0000 On Mon, May 06, 2013 at 06:32:37AM -0700, Richard Sharpe wrote: R> On Mon, May 6, 2013 at 6:28 AM, Gleb Smirnoff wrote: R> > On Mon, May 06, 2013 at 06:26:14AM -0700, Richard Sharpe wrote: R> > R> Thank you for that answer. I don't have the option to install FreeBSD R> > R> 9.1. Maybe we will move to 9.1 in the future. R> > R> R> > R> However, I now understand the issues better. Of course that does R> > R> complicate my proposal on Samba technical, just a little. R> > R> > I don't understand the proposal. Samba correctly compiles with support R> > for the discussed socket options on those operating systems that support R> > them. No "fixes" to Samba are required, everything works correctly. R> R> Perhaps there are others out there like us who have to stick with R> earlier versions of FreeBSD where the symbols Samba currently uses are R> not supported. R> R> In the spirit of few or no surprises for users, a small amount of R> #ifdef stuff will work. R> R> Of course, my fellow Samba team members might decide that it is not worth it. No, small amount of ifdef stuff would not work. FreeBSD 8.0 doesn't have these socket options, you can't bring support for them defining their values. Even if you manage to compile samba with support for these socket options, it will fail at runtime, getting EINVAL error from the setsockopt() system call. -- Totus tuus, Glebius.