Sponsored Content
Full Discussion: NFS, AD, AutoFS
Operating Systems Linux Red Hat NFS, AD, AutoFS Post 302940509 by cjhilinski on Monday 6th of April 2015 04:12:51 PM
Old 04-06-2015
NFS, AD, AutoFS

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. There are no local users (other than the normal ones) on the RH7 machine...all users are defined in AD. Users can log in and an "id -a username" shows their expected UID/GID/etc. Autofs is set up on the RH7 machine so when a user logs in, it automatically mounts his/her home directory from the 2008R2 machine.

Simple as rain, as the oracle said. However, when a user logs into the RH7 machine, autofs successfully mounts the home directory (no errors with autofs logging set to debugging) but the user and group of the home directory is always set to anonymous (4294967294) instead of the user's ID and GID.

Anyone have any ideas?

Last edited by cjhilinski; 04-06-2015 at 05:14 PM.. Reason: clarification of expectations on permissions
 

10 More Discussions You Might Find Interesting

1. AIX

Autofs

Hi Guys, Autofs works fine on AIX 5.2, but the same thing is not getting mounted automatically on AIX 5.3.. Is there ant difference for autofs confiiguration between 5.2 and 5.3 Thanks & Regards Manu (0 Replies)
Discussion started by: b_manu78
0 Replies

2. Solaris

disabling nfs and autofs in solaris 9

Hi, I want to permanently disable nfs and autofs in solaris 9, (2 Replies)
Discussion started by: manoj.solaris
2 Replies

3. Solaris

autofs vs nfs

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. Solaris

autofs

hi tell me difference between direct automount and indirect automount. thanks you (1 Reply)
Discussion started by: sijocg
1 Replies

5. Solaris

Autofs

what are all the advantages of direct map and indirect map in 'AUTOFS' and which one is better for our usage (2 Replies)
Discussion started by: dinu
2 Replies

6. UNIX for Dummies Questions & Answers

NFS issue with autofs in CentOS 6.3

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

7. Red Hat

How to mount NFS using automounter(autofs)?

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

8. Red Hat

Autofs issue

Hi I'm trying to use autofs to mount a directory structure. I have a directory with sub directories in it and all of them mounted on their respective filesystems /dbname /dev/mapper/vg_dbname-Home /dbname/oracle00 /dev/mapper/vg_dbname-Data00... (3 Replies)
Discussion started by: maverick_here
3 Replies

9. Red Hat

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... (2 Replies)
Discussion started by: mrmurdock
2 Replies

10. Fedora

Autofs problem

Hi all, I'm having trouble getting autofs working on a new install of Scientific Linux 7.2. I have the files /etc/auto.master, /etc/auto/homes and /etc/auto.misc and /auto.direct setup, and they are copies of files on a working SL 6 machine. I can include the contents of the files at the end... (0 Replies)
Discussion started by: HuntWilliamR
0 Replies
FS_EXPORTAFS(1) 					       AFS Command Reference						   FS_EXPORTAFS(1)

NAME
fs_exportafs - Configures export of AFS to clients of other file systems SYNOPSIS
fs exportafs -type <exporter name> [-start <start/stop translator (on | off)>] [-convert <convert from afs to unix mode (on | off)>] [-uidcheck <run on strict 'uid check' mode (on | off)>] [-submounts <allow nfs mounts to subdirs of /afs/.. (on | off)>] [-help] fs exp -t <exporter name> [-st <start/stop translator (on | off)>] [-c <convert from afs to unix mode (on | off)>] [-u <run on strict 'uid check' mode (on | off)>] [-su <allow nfs mounts to subdirs of /afs/.. (on | off)>] [-h] DESCRIPTION
The fs exportafs command sets (if the -start argument is provided) or reports (if it is omitted) whether the machine can reexport the AFS filespace to clients of a non-AFS file system. To control certain features of the translation protocol, use the following arguments: o To control whether the UNIX group and other mode bits on an AFS file or directory are set to match the owner mode bits when it is exported to the non-AFS file system, use the -convert argument. o To control whether tokens can be placed in a credential structure identified by a UID that differs from the local UID of the entity that is placing the tokens in the structure, use the -uidcheck argument. The most common use is to control whether issuers of the knfs command can specify a value for its -id argument that does not match their local UID on the NFS/AFS translator machine. o To control whether users can create mounts in the non-AFS filespace to an AFS directory other than /afs, use the -submounts argument. OPTIONS
-type <exporter name> Names the alternate file system to which to reexport the AFS filespace. The only acceptable value is "nfs", in lowercase letters only. -start on =item -start off Enables the local machine to reexport the AFS filespace if the value is "on", or disables it if the value is "off". Omit this argument to report the current setting for all of the configurable parameters. -convert on =item -convert off Controls the setting of the UNIX group and other mode bits on AFS files and directories exported to the non-AFS file system. If the value is "on", they are set to match the owner mode bits. If the value is "off", the bits are not changed. If this argument is omitted, the default value is "on". -uidcheck on =item -uidcheck off Controls whether tokens can be placed in a credential structure identified by a UID that differs from the local UID of the entity that is placing the tokens in the structure. o If the value is on, the UID that identifies the credential structure must match the local UID. With respect to the knfs command, this value means that the value of -id argument must match the issuer's local UID on the translator machine. In practice, this setting makes it pointless to include the -id argument to the knfs command, because the only acceptable value (the issuer's local UID) is already used when the -id argument is omitted. Enabling UID checking also makes it impossible to issue the klog and pagsh commands on a client machine of the non-AFS file system even though it is a system type supported by AFS. For an explanation, see klog(1). o If the value is off (the default), tokens can be assigned to a local UID in the non-AFS file system that does not match the local UID of the entity assigning the tokens. With respect to the knfs command, it means that the issuer can use the -id argument to assign tokens to a local UID on the NFS client machine that does not match his or her local UID on the translator machine. (An example is assigning tokens to the MFS client machine's local superuser "root".) This setting allows more than one issuer of the knfs command to make tokens available to the same user on the NFS client machine. Each time a different user issues the knfs command with the same value for the -id argument, that user's tokens overwrite the existing ones. This can result in unpredictable access for the user on the NFS client machine. -submounts on =item -submounts off Controls whether a user of the non-AFS filesystem can mount any directory in the AFS filespace other than the top-level /afs directory. If the value is "on", such submounts are allowed. If the value is "off", only mounts of the /afs directory are allowed. If this argument is omitted, the default value is "off". -help Prints the online help for this command. All other valid options are ignored. OUTPUT
If the machine is not even configured as a server of the non-AFS file system, the following message appears: Sorry, the <file_system>-exporter type is currently not supported on this AFS client If the machine is configured as a server of the non-AFS file system but is not currently enabled to reexport AFS to it (because the -start argument to this command is not set to "on"), the message is as follows: '<file_system>' translator is disabled If the machine is enabled to reexport AFS, the following message precedes messages that report the settings of the other parameters. '<file_system>' translator is enabled with the following options: The following messages indicate that the -convert argument is set to "on" or "off" respectively: Running in convert owner mode bits to world/other mode Running in strict unix mode The following messages indicate that the -uidcheck argument is set to "on" or "off" respectively: Running in strict 'passwd sync' mode Running in no 'passwd sync' mode The following messages indicate that the -submounts argument is set to "on" or "off" respectively: Allow mounts of /afs/.. subdirs Only mounts to /afs allowed EXAMPLES
The following example shows that the local machine can export AFS to NFS client machines. % fs exportafs nfs 'nfs' translator is enabled with the following options: Running in convert owner mode bits to world/other mode Running in no 'passwd sync' mode Only mounts to /afs allowed The following example enables the machine as an NFS server and converts the UNIX group and other mode bits on exported AFS directories and files to match the UNIX owner mode bits. % fs exportafs -type nfs -start on -convert on The following example disables the machine from reexporting AFS to NFS client machines: % fs exportafs -type nfs -start off PRIVILEGE REQUIRED
The issuer must be logged in as the local superuser root. SEE ALSO
klog(1), knfs(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FS_EXPORTAFS(1)
All times are GMT -4. The time now is 02:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy