Path: utzoo!utstat!news-server.csri.toronto.edu!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!uwm.edu!rpi!tale From: tale@cs.rpi.edu (David C Lawrence) Newsgroups: news.software.nntp Subject: Re: NNTP or NFS for sharing news? Message-ID: <%}Y$#F=@rpi.edu> Date: 19 Jul 90 20:05:57 GMT References: <1990Jul18.233115.25423@phri.nyu.edu> Organization: Rensselaer Polytechnic Institute, Troy NY Lines: 19 It dpeends largely on where you can spare the resources. You can hammer the server a lot more by having upwards of 20 nntpd processes running on it simultaneously than you would by having 6 or 8 nfsds. The trade-off with using NFS is that the response time will be a little slower even if the load on the server is on the light side. The gain of NFS is that you can locally access all of the mounted directory, not just whatever the NNTP server wants to tell you about (which is pretty much just the active file and the articles). I miss that latter feature on turing here as there are several things that I put in rpi.edu:/usenet, from administrative files to news sources to news information, that I would like to have locally available for mailing to people or leisurely perusal but instead I must log into the server, either directly or through ftp, to transfer them to turing before I can redistribute. A minor annoyance at best but I think I will soon get /usenet mounted here too. -- (setq mail '("tale@cs.rpi.edu" "tale@ai.mit.edu" "tale@rpitsmts.bitnet"))