From owner-freebsd-stable Sun Apr 13 11:53:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA18818 for stable-outgoing; Sun, 13 Apr 1997 11:53:54 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA18804 for ; Sun, 13 Apr 1997 11:53:43 -0700 (PDT) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.5/8.8.2) id UAA15714; Sun, 13 Apr 1997 20:53:19 +0200 (MET DST) From: Guido van Rooij Message-Id: <199704131853.UAA15714@gvr.win.tue.nl> Subject: Re: NFS: Problem with portmap (fwd) In-Reply-To: from Michael Ranner at "Apr 13, 97 11:53:31 am" To: rmike@sbox.tu-graz.ac.at Date: Sun, 13 Apr 1997 20:53:19 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Ranner wrote: > > That means, if I run the nfs client software from FTP Software, I will > get this problem, right? I have to check this, but I think you are right. > There should be some option not to use callit. The FTP software uses a rather intrusive method to check for NFS servers on a LAN. > It is possible, that the error on "rpcinfo -b nfs 2" (even on localhost) > only appears after a mount from the FTP inc client. I rebooted the > machine and tried "rpcinfo -b nfs 2" and there was no error message, but > there was no try to mount from the PC before. I don;t really know.. -Guido