From owner-freebsd-net  Wed Feb 19 16:18:32 2003
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 29C4137B401
	for <freebsd-net@freebsd.org>; Wed, 19 Feb 2003 16:18:31 -0800 (PST)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A3A5F43F85
	for <freebsd-net@freebsd.org>; Wed, 19 Feb 2003 16:18:30 -0800 (PST)
	(envelope-from hsu@FreeBSD.org)
Received: from FreeBSD.org ([63.193.112.125])
 by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18
 2002)) with ESMTP id <0HAK00GSEZIU9R@mta5.snfc21.pbi.net> for
 freebsd-net@freebsd.org; Wed, 19 Feb 2003 16:18:30 -0800 (PST)
Date: Wed, 19 Feb 2003 16:24:20 -0800
From: Jeffrey Hsu <hsu@FreeBSD.org>
Subject: Re: Web100 for FreeBSD
In-reply-to: Message from Jon Dugan <jdugan@ncsa.uiuc.edu>
 "of Wed, 19 Feb 2003 16:19:01 CST." <20030219221900.GA2596@ncsa.uiuc.edu>
To: Jon Dugan <jdugan@ncsa.uiuc.edu>
Cc: freebsd-net@freebsd.org
Message-id: <0HAK00GSFZIU9R@mta5.snfc21.pbi.net>
MIME-version: 1.0
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org

  >  I have chosen to use the sysctl interface for my initial
  > implementation.  So far this is working out well, I am reading 4 variables
  > about each connection via sysctl.  Is sysctl the right way to get this
  > information?

Yes, last time I looked at the Web100 project, I thought sysctl was ideally
suited for this.

  > In order to tune a TCP connection it will be necessary to write to some of
  > the sysctl OIDs.  AFAIK only root can write to sysctl.  I can see two
  > alternatives to solving this problem:  1) using a proxy daemon which runs
  > as root to handle the updates or 2) add a permissions system to sysctl.
  > Option 2 seems like quite a lot of work and I'm not certain it is generally
  > useful.  Any thoughts?

If by option 1), you mean a setuid program that uses sysctl() and
sysctlbyname() to set the TCP connection parameters, that's what I
would recommend.

  > We are interested in receiving asychronous notification of events within a
  > particular TCP session in userland.  I am planning to use the kqueue
  > mechanism to provide this.

Sounds about right.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message