Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: pvo1478@oce.orst.edu (Paul V. O'Neill)
Newsgroups: comp.sys.sun
Subject: Re: ypbind & NFS mount problems
Keywords: Software
Message-ID: <8903120321.AA26166@sapphire.oce.orst.edu>
Date: 30 Mar 89 00:32:27 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 18
Approved: Sun-Spots@rice.edu
Original-Date: Sat, 11 Mar 89 19:21:04 PST
X-Sun-Spots-Digest: Volume 7, Issue 213, message 4 of 15

> Does anyone has problems in using a 4.0 ypbind with a 3.3 ypserv ?

We have a 4.0 4/110 and a 4.0 386i getting ypservice from a 3.5 3/280.
This may not be your problem, but it is some light on the situation.  (The
following applies to 3.4 ypserv also.)

ypbind kills the portmapper on the 4.0 system.  Restarting the portmapper
and doing a ypset in rc.local immmediately after the ypbind works for us.
NFS wouldn't work w/o the portmapper, but I'd expect an RPC timeout
message if this were your problem. (Did you wait 75 seconds?)

For some reason a second ypbind call is needed in the 386i's rc.local
before YP works.

Paul O'Neill                 pvo@oce.orst.edu
Coastal Imaging Lab
OSU--Oceanography
Corvallis, OR  97331         503-754-3251