From: mea@sparta.com (Mike Anderson)
Newsgroups: comp.os.vxworks
Subject: re: NIS and NFS
Date: Mon, 14 Dec 92 18:32:53 EST
Organization: Lawrence Berkeley Laboratory, Berkeley CA
NNTP-Posting-Host: 128.3.112.16
Originator: daemon@vxw.ee.lbl.gov

Greetings!
> 
> Submitted-by tlusco@inquisitor.gsfc.nasa.gov  Mon Dec 14 11:37:47 1992
> Submitted-by: tlusco@inquisitor.gsfc.nasa.gov (C. Tom Lusco)
>  
> 
> Our site recently implemented the NIS on the machine serving all
> our vxWorks cpus for boot files.  Now that NIS works, our vxWorks
> CPUs can no longer access by NFS.  The cpus are all in the hosts maps,
> but do not have a domain name.  Could this be the problem? 
> 
> Is it something else?  Has anyone else had problems with NIS, NFS and vxWorks?

  It's probably not the domain name.  There are several issues that may
need to be addressed.  First, look at the /etc/exports file on the NFS
server to verify that each of your VxWorks targets have permission to 
access to the files they are trying to reach.  A "showmount -e" on the
server should be most enlightening.  If your targets don't show up and
your showmount doesn't indicate the "everyone" has access to the filesystem
in question, then you'll need to add the VxWorks targets explicitly in 
the /etc/netgroup file and remake NIS.  Once NIS is remade, edit your
/etc/exports file to add the new netgroup and do an "exportfs -va".  This
may be part, but not all of your problem.  

  The next thing you have to do is to make sure that the VxWorks targets
are identifying themselves properly to the server.  This is done using
the nfsAuthUnixPrompt or nfsAuthUnixSet commands.  On each access to
the server, there are authentication parameters that are passed from
the client to the server that indicate the user ID (UID) and group ID
(GID) of the user making the request (i.e., the VxWorks target).  This
is different from the "iam" identifier and must be specified as the
numbers for the correct user from the /etc/passwd file like so:

        UID GID
         |  |
vxuser::136:9:VxWorks User:/usr/vxWorks-stuff:/bin/csh

nfsAuthUnixSet("host", 136, 9, 0, 0) would set up the target so
it could access via NFS any file owned by "vxuser" or accessible
via group #9 (provided the /etc/exports was configured correctly).

Hope this helps,


==============================================================================
    AAAA  D D    D D    EEEEE   M   M  TM  // AAAA RRRR  TTTTTT SSSSS EEEEE TM
   A   A  D   D  D   D  E      M M M M    // A   A R   R   TT   S     E
  AAAAAA  D   D  D   D  EEEEE  M  M  M   // AAAAAA RRRR    TT    SSS  EEEEE
 A     A  D   D  D   D  E      M     M  // A     A R  R    TT       S E
A      A  D D    D D    EEEEE  M     M // A      A R   R   TT   SSSSS EEEEE

Process Distribution/Control and Communications for Distributed Systems

Mike Anderson                       Voice: (703) 448-0210 ext. 235
Director, ADDEM(TM) Project Office  FAX:   (703) 734-3323
SPARTA, Inc.                        EMAIL: mea@sparta.com
Suite 900                     
7926 Jones Branch Drive        "It is useless for sheep to pass resolutions 
McLean, VA  22102               in favor of vegetarianism while wolves remain
                                of a different opinion."

                                   William R. Inge, D.D.
==============================================================================