Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: apctrc!trc.amoco.com!zjat02@uunet.uu.net (Jon A. Tankersley)
Newsgroups: comp.sys.sun
Subject: Re: ypbind & NFS mount problems
Keywords: Networks
Message-ID: <735@apctrc.UUCP>
Date: 30 Mar 89 18:43:14 GMT
References: <EHO.89Mar3233151@reason.Princeton.EDU>
Sender: usenet@rice.edu
Organization: Amoco Production Company, Tulsa Research Center
Lines: 14
Approved: Sun-Spots@rice.edu
Original-Date: 21 Mar 89 22:14:19 GMT
X-Sun-Spots-Digest: Volume 7, Issue 216, message 2 of 13

YES!!!!!!!!!!!!!!!!!

(sorry, but I thought we were the only ones.....)

We are having identical problems on 3 subnets.  There are some patches
from Sun to ypbind, portmap, etc....  Call you support people or the local
office.  The patches have fixed one subnet, don't seem to work on another,
and are not installed at all on the third.  I've been losing hair over
this one.  One workaround if you have source is to try to recompile mount
without -O.  Sun doesn't know yet what is happening to cause it, my core
dump of mount is currently being analyzed.

Are you running with subnetting or with named perchance?
-tank-