09-08-2011
If you are using NFS filesystem, you will need to change it on host filer23 (the NFS server) or export with no root squash or similiar option.
If you don't have user/group on NFS server to which you want to change ownership, you can use uid:gid on NFS server as numbers not actual names.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm kicking Unix questions out like Bruce Lee. So I'm copying a directory of files, in each directory I inevitablly get this:
I get that for usually the same set of directories/files in each folder. Is there a way to override this when copying files? (4 Replies)
Discussion started by: JPigford
4 Replies
2. UNIX for Dummies Questions & Answers
I am trying to run chown and chmod from a script owned by root. The permissions are set to 4755 so that users can execute the script as root. However, when I run the script as a user other than root, I get "Operation not permitted" for both chown and chmod. Any ideas as to why this is? (6 Replies)
Discussion started by: johnmsucpe
6 Replies
3. Programming
Hello,
I am trying to port some testtools we wrote from solaris to redhat linux(AMD64). If I link dynamic, set the correct LD_LIBRARY_PATH, everything runs fine.
If I try to link static, the pthread_create returns "operation not permitted" (error code 1).
Does anybody have an idea where to... (1 Reply)
Discussion started by: Micky
1 Replies
4. Shell Programming and Scripting
Hi - I have a script (.ksh) which has been transferred from one Linux box to another. Basically it untars a file a deploys the code to the relevent directories. It is failing with ' Cannot utime: Operation not permitted'
When I run the command by hand it *is* doing the untar to the directories... (1 Reply)
Discussion started by: ajcannon
1 Replies
5. UNIX for Dummies Questions & Answers
Hi
I executed command "chown -R xxx:xxx /" with user root... and it was too late when I found the mistake. Ownership of some files under the root directory had already become xxx:xxx. Is there a way that can recovery the ownership of all my files back to the point where they were? I really thanks. (2 Replies)
Discussion started by: password636
2 Replies
6. Linux
Hi i have written one backup script in linux workstation.The backup script will do zipping files and moved to the backup directory(i,e /net/ts-bcn/sb_backup/sand).
#So while moving zipped files to the backup directory i am getting some error like this
error:mv:failed to preserve ownership... (2 Replies)
Discussion started by: yogks
2 Replies
7. AIX
Hi all,
iam unable to mount exported directory hari on AIX 5.3,
which was in RedHat Linux As4.
Linux-server
AIX -client
I am facing errors of
bash-3.00# mount -n linuxas4 /hari /hari
mount: 1831-008 giving up on:
linuxas4:/hari
vmount: Operation not permitted.
Pl any body... (1 Reply)
Discussion started by: haribabu
1 Replies
8. Shell Programming and Scripting
Hi,
Thanks for looking into this.
I am running into below situation in free BSD.
I have a file in /tmp/sample.txt with owner as 'xyz' and group as 'wheel'
I am moving it to my home dir/newsample.txt whihc has owner 'xyz', but group 'someother' with below command, getting warning, but it is... (2 Replies)
Discussion started by: ramanaraoeee
2 Replies
9. Red Hat
RHEL 6.3
Could someone tell me how to use the find and chown command to replace all files in a directory owned by user1 (for this example) and replace with user1:group1? Most importantly I dont want to change any files owned by root. I recently used the following command but it changed the root... (4 Replies)
Discussion started by: gps1976
4 Replies
10. UNIX for Beginners Questions & Answers
Hello,
Since over one week, I have been consistently searching for a solution to my mysql installation errors. I surfed many sites on google to get rid of the issue. Now google gives me all the same results, I tested many of those solutions provided by... Now I am pulling hair
I am under... (12 Replies)
Discussion started by: baris35
12 Replies
nfssec(5) File Formats Manual nfssec(5)
NAME
nfssec - overview of NFS security modes
DESCRIPTION
The mount_nfs(1M) and share_nfs(1M) commands each provide a way to specify the security mode to be used on an NFS filesystem through the
option. mode can be either or These security modes may also be added to the automount maps. Note that mount_nfs(1M) and automount(1M) do
not support at this time.
The option on the share_nfs(1M) command line establishes the security mode of NFS servers. If the NFS connection uses the NFS Version 3
protocol, the NFS clients must query the server for the appropriate mode to use. If the NFS connection uses the NFS Version 2 protocol,
then the NFS client uses the default security mode, which is currently NFS clients may force the use of a specific security mode by speci-
fying the option on the command line. However, if the filesystem on the server is not shared with that security mode, the client may be
denied access.
If the NFS client wants to authenticate the NFS server using a particular (stronger) security mode, the client wants to specify the secu-
rity mode to be used, even if the connection uses the NFS Version 3 protocol. This guarantees that an attacker masquerading as the server
does not compromise the client.
The NFS security modes are described below. Of these, the modes use the Kerberos V5 protocol for authenticating and protecting the shared
filesystems. Before these can be used, the system must be configured to be part of a Kerberos realm.
Use authentication. The user's UNIX user-id and group-ids are passed in the clear on the network, unauthenticated by the NFS server
. This is the simplest security method and requires no additional administration. It is the default used by HP-UX NFS Version 2
clients and HP-UX NFS servers.
Use a Diffie-Hellman public key system
which is referred to as in the forthcoming Internet RFC).
Use Kerberos V5 protocol to authenticate users before granting access
to the shared filesystem.
Use Kerberos V5 authentication with integrity checking (checksums) to
verify that the data has not been tampered with.
User Kerberos V5 authentication, integrity checksums, and privacy protection
(encryption) on the shared filesystem. This provides the most secure filesystem sharing, as all traffic is encrypted. It should
be noted that performance might suffer on some systems when using depending on the computational intensity of the encryption
algorithm and the amount of data being transferred.
Use null authentication
NFS clients using have no identity and are mapped to the anonymous user by NFS servers. A client using a security mode other
than the one with which an HP-UX NFS server shares the filesystem has its security mode mapped to In this case, if the filesystem
is shared with users from the client are mapped to the anonymous user.
WARNINGS
lists the NFS security services. Do not edit this file. It is not intended to be user-configurable.
FILES
NFS security service configuration file
SEE ALSO
automount(1M), mount_nfs(1M), share_nfs(1M), rpc_clnt_auth(3N), secure_rpc(3N), nfssec.conf(4).
nfssec(5)