From owner-freebsd-questions Tue Apr 23 08:19:29 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA09960 for questions-outgoing; Tue, 23 Apr 1996 08:19:29 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA09940 Tue, 23 Apr 1996 08:19:21 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA29533; Tue, 23 Apr 1996 10:18:09 -0500 From: Joe Greco Message-Id: <199604231518.KAA29533@brasil.moneng.mei.com> Subject: Re: Bandwidth limited FTP server To: wollman@lcs.mit.edu (Garrett Wollman) Date: Tue, 23 Apr 1996 10:18:09 -0500 (CDT) Cc: ishort@pcm.co.za, questions@freebsd.org, isp@freebsd.org In-Reply-To: <9604231504.AA07538@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 23, 96 11:04:30 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > < said: > > > The easiest way to limit bandwidth is to insert a sleep() call after write() > > in your favorite network utility (here, ftpd). Limiting the number of users > > is trivial, most enhanced ftpd's will do that automatically, based on config > > file. > > This won't work in the standard ftpd because we write the entire file > in a single call to write(2). Detail. It can be broken up... > Maybe by the end of this year we'll manage to make a public release of > ISPS and then you can configure a link-share class for FTP data.... (I > wouldn't hold my breath, though, as trying to get code out of my boss > is like trying to get code out of Van Jacobson.) We need all the nifty tools we can get. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968