Xref: utzoo news.software.b:1544 news.software.nntp:67 Path: utzoo!attcan!uunet!husc6!tut.cis.ohio-state.edu!allosaur.cis.ohio-state.edu!bob From: bob@allosaur.cis.ohio-state.edu (Bob Sutterfield) Newsgroups: news.software.b,news.software.nntp Subject: Re: Reading news: NNTP v.s. NFS for access to the database Message-ID: <19675@tut.cis.ohio-state.edu> Date: 10 Aug 88 17:46:04 GMT References: <1167@luth.luth.se> <166@cvbnet2.UUCP> Sender: news@tut.cis.ohio-state.edu Organization: The Ohio State University Dept of Computer & Information Science Lines: 24 In article <166@cvbnet2.UUCP> aperez@cvbnet2.UUCP (Arturo Perez Ext.) writes: |...Our configuration here has the NNTP server machine on a different |sub-net than the one that I log onto. When I mount the NEWS |directory response time is anywhere from 1 minute to 1/2 hour. Don't |know why but I would guest that the NFS udp packets take too long on |the round trip forcing all kinds of retransmissions and other messy |things... Sounds like a severly misconfigured NFS installation. It might have been a severely overloaded gateway if you hadn't said that NNTP performs fine. |With NNTP, I can read ALL my newsgroups within 1/2 hour. I was |really disgusted (still am) with NFS once I found that out. The problem and solution don't lie in the difference between NFS and NNTP. You should be "really disgusted" (but be nice anyway :-) with whoever set up your systems, rather than with NFS. You need to spend some time looking at the retry, timeo, and retrans parameters in your client /etc/fstab entries for mounting NFS filesystems. -=- Bob Sutterfield, Department of Computer and Information Science The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277 bob@cis.ohio-state.edu or ...!{att,pyramid,killer}!cis.ohio-state.edu!bob