From owner-freebsd-hackers Mon Mar 10 15:30:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA06996 for hackers-outgoing; Mon, 10 Mar 1997 15:30:18 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA06984 for ; Mon, 10 Mar 1997 15:30:10 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.4) id SAA02191; Mon, 10 Mar 1997 18:30:01 -0500 (EST) Date: Mon, 10 Mar 1997 18:30:01 -0500 (EST) From: Charles Henrich Message-Id: <199703102330.SAA02191@crh.cl.msu.edu> To: taob@vex.net, freebsd-hackers@freebsd.org Subject: Re: freebsd as a news server? Newsgroups: lists.freebsd.hackers References: <5g1uk0$7v0$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >On Sun, 9 Mar 1997, Tom Samplonius wrote: >> >> But isn't choosing block and fragment sizes very important as well? > I would imagine so, but the default values chosen by newfs appear >to work quite well. I just bump up the number of inodes reserved on a >news spool filesystem; everything else uses the default values. I use newfs -b 4096 -f 1024 -i 1024 ccd0c, it appears the -i 1024 may be a bit of overkill given Im currently only using 20% of the inodes on a 22gb news spool. Perhaps bumping it to 2048 would be a good thing. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich