My thanks to everyone who responded (see below).
I followed Luca Pizzinato's advise and did an export with the "anon=0"
option and my problems were resolved.  Thanks a bunch!
        Ju-Lien Lim
        jlim@oxhp.com
>----------
>From: 	fpardo@tisny.com[SMTP:fpardo@tisny.com]
>
It is a security feature of NFS. User "root" is treated as user "nobody"
>when accessing NFS-mounted disks. You can read up on it in the O'Reilly
>book titled "Managing NIS and NFS" (or something like that).
>
>--
>  Frank Pardo  <fpardo@tisny.com>
>  Transaction Information Systems
>  New York City
>
>----------
>From: 	Luca Pizzinato[SMTP:Pizzinato@eumetsat.de]
>
>Hi.
>I think you should export the NFS mount with the "anon=0" option.  Then, in
>order to retail ownership etc., you could use tar in pipe, like the
>following:
>( cd /orig ; tar cpf - ./* )  |  (  cd /dest ;  tar xpvf - )
>
>Luca Pizzinato
>pizzinato@eumetsat.de
>                                                                             
>                                                                             
>                                                                             
>                                                                             
>                                                                             
>                                                                             
>                                                                             
>                                                                             
>                                                                             
>                                                                             
>                                   
>----------
>From: 	Casper Dik[SMTP:casper@holland.Sun.COM]
The root access is implemented in the server so if you have this problem
>on the Solaris clients of the HP server, you better recheck teh root exports.
>
>The root -> nobody translation happens on the server, the client has no
>influence over it (and Solaris woudl translate back to uid 60002; not uid
>65534 (known as nobody4 in Solaris 2.5.1)
>
Make sure you use teh exact name as return by gethostbyaddr for the
>Solaris clients.
>
>Casper
>
>----------
>From: 	Coffindaffer, Virginia[SMTP:Virginia.Coffindaffer@wang.com]
>Sent: 	Wednesday, July 09, 1997 2:25 PM
>To: 	'Ju-Lien Lim'
>Subject: 	RE: Questions on copying files to an NFS mount
>
>There is a patch that fixes cp -p for Solaris 2.5 - 103162-01  but I thought
>it was fixed in 2.5.1.
>
>coffindv@wangfed.com
>
>> ----------
>> From: 	Ju-Lien Lim
>> Reply To: 	Ju-Lien Lim
>> Sent: 	Tuesday, July 8, 1997 9:37 AM
>> To: 	'Sun Mailing List'
>> Subject: 	Questions on copying files to an NFS mount
>> 
>> As root on Solaris 2.5.1, is it normal that when you do a mkdir or
>> copy
>> files (even with cp -p ) to an NFS mount, it will not retain the
>> ownership of the files you're copying or does not take on the
>> ownership
>> of root when you do a mkdir.  What I get is the owner is nobody4 and
>> group is other.  Why is this.  Also, even though the NFS mount is
>> being
>> exported to give root access to the Sun workstation, it still does not
>> have "full" root access to look at all directories on the NFS mount
>> (unlike with HP-UX where this is not an issue at all).  Instead I get
>> permission denied, if I try to list the contents of one of the home
>> directories on the NFS mount.   Is this a security feature of Solaris
>> 2.5.1?  Is there a fix for it?  Or am I missing something?
>> 
>> Would appreciate your insight into the matter.  Thanks in advance.
>> 
>> 	Ju-Lien Lim
>> 	jlim@oxhp.com
>> 
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:58 CDT