From owner-freebsd-isp Sun Apr 13 02:55:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA26639 for isp-outgoing; Sun, 13 Apr 1997 02:55:25 -0700 (PDT) Received: from mixcom.mixcom.com (mixcom.mixcom.com [198.137.186.100]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA26634 for ; Sun, 13 Apr 1997 02:55:21 -0700 (PDT) Received: by mixcom.mixcom.com (8.6.12/2.2) id EAA25942; Sun, 13 Apr 1997 04:56:37 -0500 Received: from p75.mixcom.com(198.137.186.25) by mixcom.mixcom.com via smap (V1.3) id sma025890; Sun Apr 13 09:56:09 1997 Message-Id: <3.0.32.19970413044843.00d08c04@mixcom.com> X-Sender: sysop@mixcom.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 13 Apr 1997 04:48:44 -0500 To: John-Mark Gurney From: "Jeffrey J. Mountin" Subject: Re: Some advice needed. Cc: isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:33 AM 4/13/97 -0700, John-Mark Gurney wrote: >yes... but we are talking about a terminal server... they have very small >memory foot prints as you normally don't run much on one... right now my >diskless termserver has a HUMONGOUS size of 13megs... hmm... something >must be wrong... the last time I checked it was only 6-7megs... of course >I can login to it via serial console and get plenty of stats from the >machine... Yarg. Long running thread. OK then. I'd still say 16, to avoid swapping and from a security point this system will just do the term server, I guess. >would people be interested in a remote statistics gathering program? you >would run a small daemon on the terminal server (or anything else) then >you could connect to the machine with a client and obtain any info you >might want from it... What kind of stats? Any? In that case... ;-) >hmm... interesting.. I would think that PCI would keep the host processor >a bit more free to do other things... guess I'll have to finally invest in >a PCI ethernet addapter for my maine server... ttyl... Threw me off at first, so I rebooted all the servers on one segment of the network. Two servers are hit almost equally hard, one with PCI and one not, a mix of PCI and 16, with one 8 of varing workload. The hardest hit server with the PCI NIC had the lowest percentage. Key word "bus mastering" I guess. I know some have advised against Intell EtherXpress 100B cards, but I like them and the 3C595 was broken in 2.1.5, which is the only other 10/100 I had around. Plans to go 100bT for certain segments later this year. ------------------------------------------- Jeff Mountin - System/Network Administrator jeff@mixcom.net MIX Communications Serving the Internet since 1990