Automounting '/home' directory under NIS+

Hi,
I am wotking on two Unix systems. One is the NIS+ master and the other is the client. I would like to automatically mount the Home directory from the client to the master by using NIS+ name service.
For that I need to make sure the 'automount' entry in target system's ' /etc/nsswitch.conf ' file is configured to use a name service such as NIS+, but I do not know how to do that. Would you please give me an hint?

You can find a file called nsswitch.nis which is configured to use all the services via nis you can open it and edit nsswitch.conf as per its syntax . otherwise the syntax is
automount nisplus files .Make sure you have a file called auto_master with a entry +auto_home to function it correctly.
Hemant
http://www.adminschoice.com

Similar Messages

  • Unable to create directories in automounted home directory

    The subject pretty much says it all.
    I'm able to create, update, and delete files in my home directory, but as soon as I try mkdir, I get a permission denied error.
    I've ensured that NFSMAPID_DOMAIN is set on both machines. Cat'ing
    /var/run/nsf4_domain show the same values on both machines.
    I'm not sure what else to check at this point.
    Any ideas?

    Strange, did you tried patch 118376-02 (intel) or 118375-02 (SPARC)? It claims to fixe the mkdir in different-NFS-domain problem, maybe it fixes more than that..
    //Magnus

  • Home Directory not mounted in Active Directory environment

    I am trying to integrate a PowerMac G5 with Leopard 10.5.2 into an Active Directory. The Mac is bound to the AD without any problems. I can authenticate with my AD account and I also see the printers. However, I have problems using the network home directories.
    If I activate "Force local home directory on startup disk" everything works as expected: The user logs in and gets a local home directory under /Users and can mount its network home directory with the finder without the need to authenticate again, so the single-sign-on works.
    However, that's not what I want - I want the user to work solely in his networked home directory, not on the local disk. So I deactivate the button "Force local home directory on startup disk", but now the mount of the home directory fails. In the system.log I see the following:
    /usr/libexec/mount_url[123]: smb_mount: open session failed!: syserr = Broken pipe
    This is printed several times. If I try to access to automounted home directory under /Network/Servers/SERVER/USER in the terminal I also get "Broken pipe".
    The strange thing: I can access the home directory with smbclient, I can also mount it with mount_smbfs, but if I try it with /usr/libexec/mount_url it fails although I use the exact same server and user directory.
    Any ideas are greatly appreciated.

    We have a similar issue here. Only the first AD User after reboot can login and the second one gets the same error as you. (see also: http://discussions.apple.com/thread.jspa?messageID=6418268)
    It looks like there is a problem with the automounter. I set the AUTOMOUNT_TIMEOUT to 60 seconds in /etc/autofs.conf, then after logout of the first user and waiting for 1 minute, the second user can log in.

  • The /home directory

    Good Day,
    While installing Catia in the /home directory, I'm getting permission errors. Normally this is where Catia has to be installed. What has changed with the /home directory under Solaris 9. It appears to be
    a reserved directory for the system.
    Ben

    /home has always been reserved for the automounter, at least since Solaris 8 :)
    If, in the past, you were able to install software into /home, it means that (at the time) you had a proper configuration set up for the user in question.
    If, for instance, you want to install something into /home/userA you need to make sure that either the NIS+ table auto_home.org_dir or the file /etc/auto_home shows where the automounter can find the physical home directory for userA. There are some shortcuts which you can take.
    For instance, you can enter one line into /etc/auto_home which ensures that ALL directories in /home get mounted from serverA:/export/home/$username (or whichever other location counts as the physical location). This line is:
    * serverA:/export/home/&
    You will of course also need to be running the automount daemon, which is started with /etc/init.d/autofs.

  • Solaris 10 NIS Client user account home directory

    Hi all,
    I am newbie of NIS in solaris and i am setting up NIS(central authentication of user) ,So related to this i have setup and server and client but
    i am getting problem while accessing user account in client side.
    in client side i can login user which i have created in server but it is not able to find its home dir .even though i added user with the -m option on server and home dir of user is created in server side .
    *(No directory! Logging in with home=/)*which i have created in NIS server.
    also i am not able to create any directories or files in the client system it says.
    bash-3.00$ mkdir a
    mkdir: Failed to make directory "a"; Permission deniedBoth the server and client have same domainname and NIS service is also running properly.
    on the server side this is the entry of the /etc/auto_home
    # Copyright 2003 Sun Microsystems, Inc. All rights reserved.
    # Use is subject to license terms.
    # ident "@(#)auto_home 1.6 03/04/28 SMI"
    # Home directory map for automounter
    +auto_home
    * SS09:/export/home/&here SS09 is the NIS server name and i can see it both server and client side .
    bash-3.00$ ypwhich
    SS09
    bash-3.00$
    bash-3.00$
    bash-3.00$ svcs nis/client
    STATE          STIME    FMRI
    online         11:53:05 svc:/network/nis/client:defaultSo please help me regarding this ...
    Thanks
    anuj
    Edited by: anuindia on Apr 16, 2009 11:02 PM
    Edited by: anuindia on Apr 16, 2009 11:03 PM

    Look over on http://docs.sun.com for the NIS guide for your version of Solaris.
    alan

  • Why can't create file under /home directory?

    I user solaris10, and login as root,I find I can't create any file or directory under /home directory! It say "operation not applicable" ,Why? I am puzzled it for a long time. Anyone could tell how to do it?
    Thanks

    For Solaris,
    /home is not an on-disk file system, it is a file system under the
    control of the automounter, and only the automounter can create
    directories/files in it.
    If you don't want the automounter to manage /home, then remove the
    "/home" entry from /etc/auto_master
    (and issue the command "automount -v" to force the file
    to be reread, or reboot).
    However, the typical setup for Solaris is to locate user's home directories
    in /export/home.
    Kapil Khanna

  • How to automount a home directory?

    Are there any docs that explain the steps necessary to configure iPlanet Directory Server 5.1 to automount a user's home directory? I'm using Solaris 8 & 9 clients.

    May help you:
    Calling VBScript from Remote Manager for Home Dir Creation

  • I relocated by Centos 5 home directory to an NFS automount, now firefox does not start. What broke?

    Fails in both Gnome and KDE. Problem depends on the location of the user home directory. If it is not on the local machine, firefox and thunderbird do not start.

    Fails in both Gnome and KDE. Problem depends on the location of the user home directory. If it is not on the local machine, firefox and thunderbird do not start.

  • Can ssh into client iMac but cannot mount home directory ...

    I've got a server running 10.4.11 and a bunch of client iMacs (10.5.n). If I ssh into a client iMac it lets me log in but cannot mount my home directory (which lives on the server). Obviously ssh is getting my credentials from the server but isn't getting (or cannot get) the information to mount my disk. If I log in through the gui on the client it all works fine. I suspect this is less of an error and more of a design. Is there a way to get the clients to mount my home when logging in with ssh? If not then Apple presumably has a reason for disallowing this behaviour. Is there a way around this? Perhaps with mount_afp?
    We want to be able to log into many client iMacs at once to run computations on them. Eventually we want to do this on a suite of XServes and XGrid. This is all very easy with linux and nfs and I was expecting the same sort of ability through OS X. I know that I can export everything from the server with nfs (though that may not solve my problem) but I only have the one system and multiple users and I can't really experiment while they are connected.
    Suggestions? Comments? If there are obvious examples of this elsewhere please point me toward them.

    Well it's never worked that way for me. Do you actually use this method to log in?
    I've gone through all of the server logs, watching what gets added as I log on to a client. I don't see anything there that suggests it is even attempting to mount the home directory. I also watched on the client and didn't see any errors. When I ssh into a client I see the following message on the terminal, "Could not chdir to home directory /Network/Servers/server.some.place/Volumes/R1/UsersR1/username: Unknown error: 118" This suggests that the client knows where my home should be but doesn't know how to mount it.
    I have enabled the basic setup on my server. User accounts have Home URLs like "afp://server.some.place/UsersR1/username" and Full Paths like "/Network/Servers/server.some.place/Volumes/R1/UsersR1" (R1 is a RAID disk). UsersR1 has been made into a Share Point and Server Admin tells me that the disk "will be automatically mounted using the AFP protocol as /Network/Servers/R1 on client machines". This part doesn't seem to be true as when I log into a client through the GUI the actual path that is mounted as my home is /Network/Servers/server.some.place/R1" (pwd in my home directory returns /Network/Servers/server.some.place/Volumes/R1/UsersR1/username which is a actually rather inconvenient).
    Under the Advanced tab in the Workgroup Manager, Accounts pane, I've got "Allow simultaneous login on managed computers". This seems to work but also seems only to apply to the GUI, that is I can log onto several clients at once.
    How do I ask a client machine what home directory information it is getting from the server for any particular user? Is there some setup on the client machines that will enable automatic mounting of homes through ssh? On the clients, the Directory Utility, which I have used to connect the client to a Directory Server, has a Mounts pane which allows me to "Edit automatic NFS mounts for this computer". I am not exporting any NFS from the server, but perhaps this is the way to make it work?
    Perhaps what I want to requires Kerberos? I don't have that enabled.
    When I have done this on a cluster of linux machines I exported the home directory from the server with NFS (exportfs) and then, using NIS and automount on the clients it "just worked". It was very simple. If it is supposed to work with Macs and OS X, it may be simple but it's not obvious.

  • Problem mounting NFS home directories of NIS users.

    Only on one of client (rest on all clients working fine), the Local directories under /home is getting mounted instead of NFS shared home directories of NIS users. Able to manually mount the NFS shared directories but they also get automatically unmount after some ideal time. Want that the NFS shared directories gets automatically mount when the NIS user gets login as it is happening on all other clients.
    Scenario:_
    NIS user: user1
    NFS Shared home directory: /export/home/user1 (which should get mount as /home/user1 when user1 gets login)
    Local directory: /home/user1 (which is getting mounted when user1 is getting login)
    [CLIENT]/--->ps -ef | grep automount
    root 23369 1 0 Mar 19 ? 1:58 /usr/lib/autofs/automountd
    [CLIENT]/--->cat /etc/auto_master
    /xfn -xfn
    /net -hosts -nosuid,nobrowse
    /- auto_direct -intr
    /- auto_home -intr
    [CLIENT]/--->ypcat -k auto.home
    /home/user1 NFS_SERVER:/export/home/user1
    /home/user2 NFS_SERVER:/export/home/user2
    [NFS_SERVER]-->cat /etc/dfs/dfstab
    share -F nfs -d "user home dir" /export/home
    [NIS_SERVER]--->cat /etc/auto_master
    /xfn -xfn
    /net -hosts -nosuid,nobrowse
    /- auto_direct -intr
    /- auto_home -intr
    Please let me know if any other information is required.

    add this entry as the first non-comment line in /etc/auto_master on the client:
    +auto_master                                                                                                                                                                                       

  • Home directory and personal website trouble after 10.6.7 Server

    Xserve recently upgraded to 10.6.7 Server and it seems to have broken two features:
    When doing Connect to Server as an LDAP user their home folder is no longer available as a mountable volume. The share that holds all user home folders IS available so that's not the end of the world.
    However this also broke the personal web sites, so going to:
    http://<serveraddress>/~shortname now just gives a 403 error
    and I get these errors in the error_log (under WebServer in Console)
    [Tue Aug 24 11:38:48 2010] [error] [client 10.2.104.16] File does not exist: /Library/WebServer/Documents/~walshd
    [Mon Apr 25 09:11:22 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    [Mon Apr 25 12:39:39 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    The sharepoint is on an old XServe RAID unit connected directly to server via FibreChannel, but that hasn't changed in a long time...only recent change was running all Software Updates which included moving up to 10.6.7 Server.
    Any ideas what I'm missing or where to start looking to resolve this?
    Thanks!

    Camelot wrote:
    When doing Connect to Server as an LDAP user their home folder is no longer available as a mountable volume. The share that holds all user home folders IS available so that's not the end of the world.
    There are so many ways of configuring home directories that this can't be answered without more information.
    For example, are you using automount to mount the user's home directory when they log in?
    or do the clients mount a static mount and their Open Directory record just includes a link to the (mounted) home directory?
    We are using automounts to get users their home folders. And when logging in at a terminal with an LDAP account you do get into your account as expected. It's only Go -> Connect to Server that won't give the home folder as a sharepoint and the web service for user sites that we agree are most likely tied together.
    I have both userdir_module and apple_userdir_module enabled at the moment, although when I tried just one or the other I was getting an Object does not exist rather than the permission error.
    I think the key to solving this is in the console log entries httpd -> error_log:
    errors before posting:
    [Tue Aug 24 11:38:48 2010] [error] [client 10.2.104.16] File does not exist: /Library/WebServer/Documents/~walshd
    [Mon Apr 25 09:11:22 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    [Mon Apr 25 12:39:39 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    [Mon Apr 25 14:40:17 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    [Wed Apr 27 06:57:03 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    [Wed Apr 27 06:57:17 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    with userdir_module disabled and apple_userdir_module enabled:
    [Wed Apr 27 06:57:32 2011] [error] [client 10.2.104.16] File does not exist: /Library/WebServer/Documents/~walshd
    [Wed Apr 27 06:57:34 2011] [error] [client 10.2.104.16] File does not exist: /Library/WebServer/Documents/~walshd
    [Wed Apr 27 06:57:35 2011] [error] [client 10.2.104.16] File does not exist: /Library/WebServer/Documents/~walshd
    [Wed Apr 27 06:57:49 2011] [error] [client 10.2.104.16] File does not exist: /Library/WebServer/Documents/~walshd
    [Wed Apr 27 06:57:50 2011] [error] [client 10.2.104.16] File does not exist: /Library/WebServer/Documents/~walshd
    with userdir_module enabled and apple_userdir_module disabled:
    [Wed Apr 27 06:58:02 2011] [error] [client 10.2.104.16] File does not exist: /Network/Servers/staff.lsrhs.net/Volumes/Staff/Home/walshd
    [Wed Apr 27 06:58:03 2011] [error] [client 10.2.104.16] File does not exist: /Network/Servers/staff.lsrhs.net/Volumes/Staff/Home/walshd
    [Wed Apr 27 06:58:04 2011] [error] [client 10.2.104.16] File does not exist: /Network/Servers/staff.lsrhs.net/Volumes/Staff/Home/walshd
    with both enabled again:
    [Wed Apr 27 06:58:22 2011] [error] [client 10.2.104.16] (62)Too many levels of symbolic links: access to /~walshd failed
    The strangest thing about this issue is that it happened  after I applied a bunch of updates last week:
    2010-04-22 12:52:17 -0400: Installed "Remote Desktop Client Update" (3.3.2)
    2010-04-22 12:52:23 -0400: Installed "AirPort Base Station Update 2010-001" (5.5.1)
    2010-04-22 12:52:39 -0400: Installed "QuickTime" (7.6.6)
    2010-04-22 12:52:41 -0400: Installed "Xserve EFI Firmware Update" (1.1)
    2010-04-22 12:52:44 -0400: Installed "iLife Support" (9.0.4)
    2010-04-22 12:52:59 -0400: Installed "Java for Mac OS X 10.5 Update 5" (1.0)
    2010-04-22 12:53:21 -0400: Installed "iTunes" (9.1)
    2010-04-22 12:54:31 -0400: Installed "Security Update 2010-003" (1.0)
    2010-04-22 12:55:16 -0400: Installed "Safari" (4.0.5)
    2010-04-22 13:15:22 -0400: Installed "Java for Mac OS X 10.5 Update 6" (1.0)
    Could any of these have broken the home directories sharepoints or is this just a huge coincidence?

  • Unable to create a user home directory ?

    When I use root to create a new account, it can not create a default home directory for this user .
    This problem will also cause a lot of other problems when using non-root account to login in.
    $ ssh [email protected]
    Password:
    Last login: Mon Jul 7 10:13:42 2008 from 10.250.X.X
    Could not chdir to home directory /home/admin: No such file or directory
    Sun Microsystems Inc. SunOS 5.10 Generic January 2005
    what's the problem ?

    chances are its the automounter. check /etc/auto_master. it by default includes /home as a mount point for the automount process. if you dont need the automount for /home, comment that line out, save the file, and run automount -v (-v for verbose output). you should then be able to create dirs under /home. or, you could use a diff home dir prefix, or use the automounter (this will take some setup).

  • Define a remote linux nfs home directory for an open directory's user

    Hi,
    I want to migrate from nis to open directory. Everything but "auto homes" looks good. As I create a user with the workgroup manager, under the 'Home' tab, I'm unable to specify a remotre nfs home directory(linux).
    So, I want client01(linux) to authenticate on macsvr01(mac osX 10.6.2 / opendirectory). When authenticated, I want macsvr01 to tell client01 that it's home directory is hosted nfs on linuxsvr01(linux nfs file server).
    When i look the workgroup manager, the only possibility seems to be 'afp'.
    When I try to specificy nfs entries, I can't validate my setting because the 'Ok' button remains grayed out.
    Any suggestions?
    Thank you,
    Luc

    I assume you are creating folders in a file server and its a windows machine , is it ?
    You can install a remote manager on file server or on any other machine in network and execute your scripts remotely using remote manager
    Also you can execute your script like wscript c:\CreateFolder.vbs
    Thanks
    Suren
    Edited by: Suren.Singh on Aug 10, 2010 3:20 PM

  • Automounting home directories

    I really like how Solaris keeps home directories at /export/home/<username> and then mounts them at /home/<username> upon login. I tried to get this same functionality with OL63 but couldn't get the automounter to work.
    My setup is:
    /etc/auto.master contains
    /home /etc/auto.homeAnd /etc/auto.home contains
    * :/export/home/&I restarted the services but when any user logs in the system complains about not having a home directory. What am I missing?

    I have not configured autofs recently, but have the following example in my notes:
    <pre>
    # cat auto.master
    /nfs-photon01 /etc/auto.photon01 vers=3,rw,hard,proto=tcp,intr
    # cat auto.photon01
    * photon01.example.com:/&
    # mkdir /nfs-photon01
    # service autofs reload
    </pre>
    Does your /etc/auto.home file specify the NFS server?
    By the way, NFS4 is default in OL6, which requires that you export all NFS directories under one virtual home. For instance, if /ext/nfs is the NFS root (fsid=0), everything else that you want to be shared over NFS4 must be accessible under /ext/nfs. Check your /etc/export file. There are examples on the web, you should be able to find it searching for "NFS4 fsid-0".

  • Mounting NFS home directory error, please help!

    Hello everyone,
    We are working on setting up a network of Macs to a Linux server. The server is running NFS / NIS to authenticate, all the users have their home directories on the server and do not have any local accounts on any of the computers.
    We have a problem getting the home dirs automounted on the local computers. The users need their home folder set correctly to import settings and so on, and the home folders are stored on the server.
    We can connect to the NFS servers, we can get the computers to log in with NIS accounts, we can manually access their restricted info once we manually mount the NFS drive.
    However, we cannot get the home folders to mount in the home directory, automounted. We have one working macintosh computer running Apple Os X 1.5, but we cannot get it to work on Snow Leopard ( 1.6 ).
    Did anything change in permissions or in the way Mac OS X handles NFS shares or automounting in the update to 1.6, Snow Leopard? Does anyone have any experience handling NFS/NIS mounting in Apple Mac OS X 1.6?
    / Z.

    Hello everyone!
    Even if I posted this recently, we had been working on it for two days. However, we just defeated this beast and managed to solve it!
    It turned out to be simple, as it often is:
    We changed /etc/auto_home to manually provide the IP of the NFS server with a wildcard (*) for users, & for username, then commented out the normal +auto_home.
    The server was already set up to allow the computers to access everything.
    The problem was, in short, that mac OS X has a dedicated slot for mounting in /home and thus you can't mount anything else there unless you replace the normal /etc/auto_home

Maybe you are looking for