Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.protocols.nfs
Subject: Re: question on showmount and mountproc_dump()
Keywords: showmount, mountproc_dump
Message-ID: <1991Feb20.041556.21719@Think.COM>
Date: 20 Feb 91 04:15:56 GMT
References: <19256@samsung.samsung.com>
Sender: news@Think.COM
Distribution: comp
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 19

In article <19256@samsung.samsung.com> ginsburg@samsung.COM (Scott Ginsburg) writes:
>  I have one host on my system that produces the "can't
>reply to host" syslog message when I direct my RPC mountproc_dump()
>call at it using a UDP transport, which results in an RPC timeout
>message on my client.  The program, however, works fine over a TCP
>transport. How is this so?

Maybe that one host has a limit on the size of UDP datagrams that is too
small to hold its entire mount list.  TCP doesn't have any size limit on
message size.

I had a similar problem in an early version of Symbolics Lisp Machine NFS
Client, which only supported UDP transport, so had problems using servers
with large export lists.
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar