Reshare mounted NFS Home Directory

Hi there,
I have a XServe with Leopard Server 10.5.8 installed.
Open Directory works fine, I mean users are known through the network and they can log on every computer with ssh, their home directory is well automounted by clients. Their home dirs are stored locally on the server.
I would try something new in order to win space:
1. create user dirs locally on the clients
2. export them on the network
3. mount them through NFS or AFP on the server and reshare it on the network as user dir.
item 1. is done : the local user get the uid and gid of the network user, permissions are OK on his home dir.
item 2. is OK : via NFS
item 3. seems OK because I mkdir /AFP-Users where I mount via NFS remote user dir (e.g. bob). Then I export /AFP-Users as automatic Users Home Dirs in addition to /Volumes/External/User where native OD accounts are.
I have specified in OD that Home dir of bob is nfs://server/AFP-Users/bob.
It works fine if I make a su - bob on the server : files are here and bob is able to write.
bob is able to ssh on every computer on the network, no error msg on login but no files! And no permissions to write.
If someone has an idea...
Thanks,
joe

Hello,
in the meantime, I have looked for Internet for my solution, nobody speaks about this precise problem.
I tried to simply mount AFP directory from a client to another, but unable to have permissions on the Terminal because the owner of the mounted AFP is local admin instead of the OD user...
I would very appreciate if anyone has an beginning of an idea.
Thanks,
joe

Similar Messages

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

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

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

Mountain lion server network accounts are not mounting network home directory, rather its creating a blank local directory

I have set up a scratch mountain lion server with open directory. copied over old user account directories and added my users that match the directory ids. Currently if a networked user logs into a networked computer, instead of mounting the network home directory, its creating a local home directory. suggestions?
thanks,
Dave

Additional info: it appears that certificates are not working either: setting up ical: "the certificate for this server was signed by an unknown certifying authority."...

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.

Time to search PATH varies by HOME directory path ?

I have a rather strange question, as I am running in a somewhat strange environment. I have a SunBlade running Solaris connected via Cisco VPN to my corporate network. After I start the VPN I run a number of mount commands to make my local environment look something like my environment in the office, including mounting my home directory onto my local workstation. I then change the value of the HOME variable to point to the nfs mount for my home directory and update the PATH so that my local (non-remote) bin directories are before the ones on my remote mounts (I use Solaris at work as well).
I've been running this way for a couple of years and it works well, but all of a sudden trying to start an application from my local system started to take a really long time. I narrowed it down to:
if I set HOME=/export/home/localuser it works fine
if I set HOME=/export/home/remoteuser (which is where my home directory is mounted) it does not
It is not the PATH itself as I have the problem even when i don't change it at all. I have a copy of dtpad in /export/home/localuser/bin and that path is the first value in the PATH variable. With HOME set the first way "time which dtpad" takes 0.269s and with it set the second way it takes 4.530s.
This does not make any sense to me. Can someone that understands how the PATH searching algorithm works shed some light on this ?
Thanks

One more thing. I delete the copy of dtpad in my home directory and let it find the real one using the PATH. With HOME set to the local directory it took 0.527s to find it. With HOME set to the remote directory it took 2.139s. Same PATH in both cases. So how does $HOME fit into the $PATH search ?

NFS Home Directories Yosemite

Has anyone successfully used NFS home directories for network logins?
This used to work in 10.6.8 Server but I am having a hard time setting it up in Yosemite. I need to enable fast user switching with multiple logins to our server which appears to be impossible using AFP.
I'd appreciate any tips on how to accomplish this. All clients and server are running clean Yosemite installs.

Apple stopped officially supporting NFS based home directories when Lion and Server.app was released. I have not done extensive testing but I certainly find two sessions using fast user switching and AFP works with Mavericks clients.
As far as I can see if a Snow Leopard server was connected to a Mavericks or Yosemite OD server it would still be possible for the Snow Leopard server to register an NFS home directory share in to Open Directory. This suggests that it might be possible to do the same even with a Mavericks or Yosemite server but that one would have to do all the work by hand in the command line. The logic for this conclusion is that Mavericks and Yosemite still include NFS even if they do not provide a GUI means to configure it and OD itself would appear to still be able to store records relating to NFS locations.
I have used NFS home directories in the past and found it solved a number of issues including -
Completely getting round Adobe's long time issues with network home directories
The same for some other third-party applications
Allowed 20+ users all on the same server to be logged in to their individual home directories in a Mac Terminal Server setup
This was all back in the days of using Snow Leopard Server.
I get the impression Apple secretly added the ability to use Fast User Switching for network logins with Lion or later to compensate for removing NFS support. This may have been at the behest of the developers of the two Mac Terminal Server products.

Setup Home Directory that is on another server?

Hi there,
I have setup a server (10.4) where each users home directory is kept on an xserve raid that is connected via fiber. When a user logs onto this server, they can mount their home folder or the other shared folder which has a bunch of stuff in it.
I also have another server (10.3) which does not have user home directories setup on it. What I would like to do is setup the 10.3 server to mount a home directory that is on the xserve raid when a user logs in. So regardless of which server they are authenticating to, the home directory that is mounted sits on the xserve raid. Again, the XServe Raid is not connected to this server (10.3)
Here are the specifications:
10.4 server: server4.local
XServe connected to it via fiber
Users on this server have the home address of: /Volumes/XServeRaid/Faculty Folders/asmith
10.3 server: serverone.local
What would the information be for the following fields on the other server?
Mac OS X Server/Share Point URL:
Path:
Home:
Thanks very much
Andrew

The way you do what you are describing is to keep the Account information in the same place it is now, but change the pointer to a User's (or collection of Users) Home Folder.
To transition to that:
• decide where the User's new Home will be.
• create a new folder for that user at the new location.
• copy the user's files to the new location.
• change the home pointer in their account record.

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

Linux users cannot open Firefox on multiple systems that are mounting the same network drive as their home directory

I am supporting a user who is logging into multiple linux systems that all have the same /home directory mounted to a network filer.
When the user opens firefox on one system, he is unable to open firefox on other systems.
I'm assuming this is because firefox is storing his profile in /home.
These are Centos 5.4 x64 systems, authenticatiing to a Windows 2003 Domain. The filer that hosts the home directories is a NetApp with both CIFS and NFS permissions enabled on the volume that /home resides. We are using the version that came with the Centos installation, 3.0.12

So while this worked well for my computer at home, it does not work for the actual computer the disk is mounted on. If I try to mount the disk as the "office" user, the computer rejects the connection to itself and tells me to access it locally. Any ideas on how to handle this? Thanks again.
dlr

Mount Home Directory when logged in locally

I want an application that would ask for the users name and then mount and open their home directory. This will be used when a user is logged on locally and not via OD/AD. Can automator do this or should i stick to apple script. Right now my apple script looks like this.
to getusername()
display dialog "Enter your username:" default answer ""
set username to text returned of result
return {username}
end getusername
to getuserpwd()
display dialog "Enter your password:" default answer "" with hidden answer
set userpwd to text returned of result
return {userpwd}
end getuserpwd
set username to getusername()
set userpass to getuserpwd()
tell application "Finder"
if (username > 161000 and username < 169999) then
open location "afp://" & username & ":" & userpass & "@wwrsdod2.wwrsd.org/HomeDirs/GY2016/" & username
else
open location "afp://" & username & ":" & userpass & "@wwrsdod2.wwrsd.org/HomeDirs/GY2015/" & username
end if
end tell
But the finder opens up to the top level of the share and not the user's folder. Anyone help me out.
Thanks

Hi Tejas,
usually when you see the server invalid (by the Yellow triangle on each repositories) means that your MDM server and MDM Clients have different version. Please, checks the version and be sure these are the same, or server version is more recent of the clients one.
Take a look to this, may be it help:
Re: Error Initialising database engine
Bye,
Vito

Mountain Lion Server: Network users Home directory mount problems

I am having several problems with my server after a latest name change of the server via Server.app. (A first name change made problems, after that I have been trying to repair, changing the name a few times more. With latest name change, I also changed the server name itself from Foo to Bar while changing domain name from domain.com to bar.domain.com after which I repaired DNS so it covers the whole domain.com domain).
The users in the Network directory think their home directory is on afp://domain.com/Users, but the server is now called bar.domain.com. /Network/Servers/bar.domain.com does not exist on the server. Client machines (with mobile home directories) are now able to sync, because I added an A record for domain.com to DNS (not nice, but does the job, or more specifically that job). Also on the clients, I can go to a SHARED folder in Finder with the name Bar and go to Users and see al the home directories there. But:
bash-3.2# ls -l /Network/Servers/
total 4
dr-xr-xr-x 2 root wheel 1 Apr 14 11:14 domain.com
dr-xr-xr-x 2 root wheel 1 Apr 14 11:14 foo.domain.com
bash-3.2# ls -l /Network/Servers/*
/Network/Servers/domain.com:
total 2
dr-xr-xr-x 2 root wheel 1 Apr 14 11:14 Users
/Network/Servers/foo.domain.com:
total 2
dr-xr-xr-x 2 root wheel 1 Apr 14 11:14 Users
bash-3.2# ls -l /Network/Servers/*/Users
/Network/Servers/domain.com/Users:
ls: Users: Input/output error
/Network/Servers/foo.domain.com/Users:
ls: Users: Input/output error
So, on the server looking for folder ~user does not work. It wants to go to afp://domain.com/Users/user but that is unreachable.
Any tips on what I can do except do a clean rebuild of the server (again)?
(One of the obvious problems is that the Realm of OD is still called foo.domain.com, the origin of my problems has been that the first name change from foo.domain.com to domain.com (ill-advised, I know) failed — partly).
What I'd like to know is:
- where is it determined which servers end up in /Network/Servers?

Som additional info:
Other machines can mount afp://foo.domain.com/, afp://domain.com/ and afp://bar.domain.com/, but the server itself cannot mount them via Finder.

Virt-install cannot mount nfs directory

Hi all,
I'm trying to use ovms but I cannot create any virtual machine.
I successfully installed OVMS; I disabled iptables to avoid network problems.
I created a dvd from Oracle Unbreakable EL 5.0 cds on a different machine.
The dvd image is shared by a linux CentOS box. The ISO image is inside /opt/tmp_os_isos/50 so I did
service nfs start
mkdir /mnt/dvd50
chmod a+rwx /mnt/dvd50
mount -o ro,loop /opt/tmp_os_isos/50/Enterprise-R5-GA-Server-i386-dvd.iso /mnt/dvd50/
exportfs *:/mnt/dvd50
and on the ovms server I did:
[root@ovms ~]# virt-install
What is the name of your virtual machine? giallo2
How much RAM should be allocated (in megabytes)? 512
What would you like to use as the disk (path)? /virtpcs/dischi/giallo
How large would you like the disk (/virtpcs/dischi/giallo2) to be (in gigabytes)? 30
Would you like to enable graphics support? (yes or no) no
What is the install location? nfs:10.10.10.242:/mnt/dvd50
And I always end up with the error
That directory could not be mounted from the server.
If I try to run
[root@ovms ~]# mount.nfs 10.10.10.242:/mnt/dvd50 /mnt/50
it works!
I also tried to build adifferent dvd iso, or to uso a OEL 4.4 dvd iso (taken from an original working oracle dvd) but I always end up with the same error
Where am I wrong?
thanks, andrea

I realized this problem was somehow related with the ovms installation: the pc I installed ovms on has two network card; when I installed ovms I configured eth0 via DHCP (eth0 is linked to the office network and to internet) and I configured eth1 with a static IP (eth 1 is connected to a "private" network made by 2 more pc).
I also choosed to manage ovnms via eth1 (the network card witch has a statis ip), and everything regardind ovms has always been done via eth1.
Now I reinstalled ovms and I choosed to manage it via eth0 (si I put a static ip address on eth0) and everything seems working: I'm just installing OEL5.0 via nfs without any problem (I hope... :-) )
andrea

10.5 clients won't login/mount home directory

Hello all,
I am having some issues with 10.5.8 clients logging in network users. At our school, we have a "magic triangle" setup -- Mac and PC clients, an Active Directory for user authentication (a Win 2k3 server DC I believe), and an Open Directory server (running 10.7.5 OS X Server) for Workgroup Managment and software updates. Along with this, there is a Linux NAS box that acts as the file server hosting the user's home directories.
I have a few test student accounts that I have set up exactly the same way that normal student accounts are added to AD. Users have complained that these 10.5.8 clients will not let any students log on, as I have verified with my test student accounts. When logging in, an error comes up that says "Logging into the account failed because an error occurred". In secure.log I get a "smb_mount: syserror = Broken pipe" line along with
ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] | PremountHomeDirectoryWithAuthentication( url=smb://fileserver.domain.org/username, homedir=/Network/Servers/fileserver.domain.org/username, name=username ) returned 32
When I turn off "Create Mobile Account at Login", the user can log in just fine, which obviously leads me to believe that there is an issue with mounting the samba share for the user's home directory during the HomeSync.
I know the client can resolve the file server's hostname by nslookup, so I don't think DNS is the issue. But I'm all out of ideas after looking everywhere online, and am hoping someone can assist me with this. I'm just a computer technician and not a network sys admin by any means, but I know a good enough amount to try to troubleshoot this. Even my network manager is stumped, and his answer is to upgrade the client to 10.6, resolving that the issue is with 10.5. I want to try to solve this issue rather than having to re-image all the 10.5 machines.
Obviously school is out for the weekend, so I won't be back for a couple days to work on the issue if anyone does respond in the next couple days.
Thanks in advance!
-Brandon

Hi Brandon, certainly no expert at this, but let me trow this out at you...
Found a work-around. This command adds a delay, in this case 45 seconds, before displaying the Login Window.
defaults write /Library/Preferences/com.apple.loginwindow StartupDelay -int 45
If the Login Window UI detects that the network servers are available when it starts, it will skip the delay, also if network servers become available before the delay expires, the Login Window UI cancels the delay and displays.
Kent

Reshare mounted NFS Home Directory

Similar Messages

Maybe you are looking for