Date: Sun, 4 Jan 1998 23:48:51 -0600 (CST) From: "James D. Butt" <jbutt@mwci.net> To: Atipa <freebsd@atipa.com> Cc: =?iso-8859-1?Q?=22Luis_E=2E_Mu=F1oz=22?= <lem@cantv.net>, freebsd-isp@FreeBSD.ORG Subject: Re: [fbsd-isp] Designing for a very large ISP Message-ID: <Pine.BSF.3.96.980104233558.19497B-100000@subcellar.mwci.net> In-Reply-To: <Pine.BSF.3.91.980104223115.7270B-100000@dot.ishiboo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > For a client/workstation environment, NFS is really cool. For an ISP, I > do not see any place it would be _required_ or recommended unless you MAIL.. Lets say that you have like lots of incomming mail more than one machine will handle... At that point you will have to have more than one MX host and possibly more than one popper machines.. All reading off of a common spool.. I know that BSDI had some file locking issues.. It has been a bit since I have thought about this... If I remember right it did not support any type of file locking. What about FreeBSD?? > were maintaining user shell space, which most places don't do. It adds > lots of network and CPU overhead, and a considerable risk, so it is best > suited for a "trusted" or secure environment, like behind a firewall, > where it doesn't get hit by the outside world. A trusted/secure enviroment is not difficult... > Them maintenance is fairly simple. If you can figure out serial > networking, NFS is a breeze! :) I should have defined my scares me to death more.. I have used NFS lots but I have never thought of the reliablity as very good... I have had a few instances of real problems caused by NFS some odd file coruption ect. We also had some really nasty situations come up with BSDI 2.0 where we would have to reboot the machine to make NFS work after clients crashing.. > > It scares me to death... I know that we will have to do it very soon > > though.... I can not think of any other solution for some situations... -------------------------------------------------------------------------- James D. Butt 'J.D.' Network Engineer Voice 319-557-8463 Network Operations Center Fax 319-557-9771 MidWest Communications, Inc. Pager 319-557-6347 241 Main St. noc@mwci.net Dubuque, IA 52001 jbutt@mwci.net --------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980104233558.19497B-100000>