Date: Wed, 19 Feb 2003 16:24:20 -0800 From: Jeffrey Hsu <hsu@FreeBSD.org> To: Jon Dugan <jdugan@ncsa.uiuc.edu> Cc: freebsd-net@freebsd.org Subject: Re: Web100 for FreeBSD Message-ID: <0HAK00GSFZIU9R@mta5.snfc21.pbi.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0HAK00GSFZIU9R>