04-26-2016
RHEL 7.1 autofs permissions do not match NFS servers
RHEL 7.1 client using autofs to mount a NIS map of home directories being exported by a Solaris 10x86 nfs server.
The owner and group are correct on the NFS server, but on the RHEL client, the owner and group end up being nobody nobody. The USERS and GROUPS are NIS maps as well. They are correct uid/gid.
Still can read and write, but this affects oracle NIS user owner/group as well.
whats happening to the translation of user and groups and how to correct it?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all
can someone tell me how to set the follwoing permissions in the /etc/exports file to share a directory.
I need 2 users eg a+b to be able to read and write to the directory but everyone else to just read. we have NIS in our environment and I though I could use netgroups do do this. My... (2 Replies)
Discussion started by: silvaman
2 Replies
2. Solaris
Hi,
I want to permanently disable nfs and autofs in solaris 9, (2 Replies)
Discussion started by: manoj.solaris
2 Replies
3. Solaris
I've a sun server, 3 sun workstations and plan to do backup on certain directory in each workstations monthly.
As it's only require to mount as NFS on those workstations once a month. So I plan to configure such requirement using autofs.
What are the considerations need to take care in such... (4 Replies)
Discussion started by: KhawHL
4 Replies
4. Red Hat
Hello all,
I am planning to deploy a configuration / auditing software package for about 100 new nodes that we are planning to install. I am hearing many good things in regards to cfengine and puppet. Can someone shed some light in regards to these solutions?
Thanks,
jaysunn (1 Reply)
Discussion started by: jaysunn
1 Replies
5. Red Hat
Hi All,
I have RHEL 5.6 with a 70GB local directory of Web content. Images, PHP scripts etc.
I need to copy all this content to an NFS array thats mounted on the RHEL server.
I did a baseline cp to copy the content one week ago. Since my baseline copy the local directory has grown by 8GB.... (2 Replies)
Discussion started by: general_lee
2 Replies
6. Red Hat
Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured
server:
/etc/hosts.allow:
all : all
all :all@all
setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies
7. UNIX for Dummies Questions & Answers
I am running CentOS 6.3 as a VM on a host which has the same installation. I configured my NFS server and I am guessing it works. I say guessing because I can mount the desired folder with mount command on my client machine. So, when I run:
mount -t nfs -o vers=3 vm2.domain.com:/nethome /nethit... (7 Replies)
Discussion started by: bashily
7 Replies
8. Red Hat
I have an nfs at 192.168.1.10:/home/vm1/Desktop/nfs and will like to mount locally to /home/vm1/Desktop/nfs-mount using automounter...need help doing do
What i did
$cat /etc/auto.master
/home/vm1/Desktop /etc/auto.nfs
$cat /etc/auto.nfs
nfs-bind -fstype=nfs ... (3 Replies)
Discussion started by: nokia3310
3 Replies
9. Red Hat
Here's my challenge. I have a RedHat7 machine running a statistical software package. It needs to NFS-mount directories from a Windows 2008R2 machine. The RH7 machine uses MSAD (Microsoft Active Directory) to handle authentication of people connecting via SSH. AD is on a separate 2008R2 machine.... (5 Replies)
Discussion started by: cjhilinski
5 Replies
10. Solaris
NFS server: RHEL:6
/nfsdb 192.168.8.10/28(rw,sync,no_root_squash) 192.168.7.10/28(rw,sync,no_root_squash)
Client: Solaris 11.3
vfstab entry :
192.168.8.9:/nfsdbarch - /archive_data nfs - yes rw,soft,vers=4
# ls -ld /archive_data
drwxr-xr-x 4 root root... (3 Replies)
Discussion started by: Shirishlnx
3 Replies
LEARN ABOUT POSIX
nischgrp
nischgrp(1) User Commands nischgrp(1)
NAME
nischgrp - change the group owner of a NIS+ object
SYNOPSIS
nischgrp [-AfLP] group name...
DESCRIPTION
nischgrp changes the group owner of the NIS+ objects or entries specified by name to the specified NIS+ group. Entries are specified using
indexed names (see nismatch(1)). If group is not a fully qualified NIS+ group name, it will be resolved using the directory search path
(see nisdefaults(1)).
The only restriction on changing an object's group owner is that you must have modify permissions for the object.
This command will fail if the master NIS+ server is not running.
The NIS+ server will check the validity of the group name prior to effecting the modification.
OPTIONS
The following options are supported:
-A Modify all entries in all tables in the concatenation path that match the search criterion specified in name. This option implies
the -P switch.
-f Force the operation and fail silently if it does not succeed.
-L Follow links and change the group owner of the linked object or entries rather than the group owner of the link itself.
-P Follow the concatenation path within a named table. This option only makes sense when either name is an indexed name or the -L
switch is also specified and the named object is a link pointing to entries.
EXAMPLES
Example 1: Using the nischgrp Command
The following two examples show how to change the group owner of an object to a group in a different domain, and how to change it to a
group in the local domain, respectively.
example% nischgrp newgroup.remote.domain. object
example% nischgrp my-buds object
This example shows how to change the group owner for a password entry.
example% nischgrp admins '[uid=99],passwd.org_dir'
In the previous example, admins is a NIS+ group in the same domain.
The next two examples change the group owner of the object or entries pointed to by a link, and the group owner of all entries in the hob-
bies table.
example% nischgrp -L my-buds linkname
example% nischgrp my-buds '[],hobbies'
ENVIRONMENT VARIABLES
NIS_PATH If this variable is set, and the NIS+ name is not fully qualified, each directory specified will be
searched until the object is found (see nisdefaults(1)).
EXIT STATUS
The following exit values are returned:
0 Successful operation.
1 Operation failed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
SEE ALSO
nis+(1), nischmod(1), nischown(1), nisdefaults(1), nisgrpadm(1), nismatch(1), nis_objects(3NSL), attributes(5)
NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
SunOS 5.10 10 Dec 2001 nischgrp(1)