From owner-freebsd-hackers Tue Sep 5 02:35:14 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.11/8.6.6) id WAA03202 for hackers-outgoing; Mon, 4 Sep 1995 22:36:07 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.11/8.6.6) with ESMTP id WAA03166 for ; Mon, 4 Sep 1995 22:35:59 -0700 Received: from Glock.COM (glock.com [198.82.228.165]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id JAA13554 for ; Mon, 4 Sep 1995 09:26:30 -0700 Received: (from mmead@localhost) by Glock.COM (8.6.11/8.6.9) id MAA06295; Mon, 4 Sep 1995 12:25:21 -0400 Date: Mon, 4 Sep 1995 12:25:21 -0400 From: "matthew c. mead" Message-Id: <199509041625.MAA06295@Glock.COM> To: hackers@FreeBSD.org Subject: any way to limit nfs request throughput? Sender: hackers-owner@FreeBSD.org Precedence: bulk I have someone that's doing some diskless booting off my machine, which he really should be purchasing his own drive for. Given that I've only got a 486/66 with 48M ram and an ne2000 clone ethernet card, his activity is slowing my machine down a lot. Is there any way to limit the nfs request frequency, or disallow more than x requests per second to alleviate some of this problem, or should I just nice -19 the nfs processes? Any other ideas? Thanks... -matt -- Matthew C. Mead mmead@Glock.COM | Network Administration and Software Development http://www.Glock.COM/~mmead/ | Consulting: BizNet Technologies -> mmead@bnt.com