But what happens in the following scenario. In client C, users user1 and user2 are both logged in and their home dirs are /server1/users/user1 and /server1/users/user2.
Now I want to move user1 to a different server server2. His home will be changed to /server2/users/user1. I can unmount /server1/users/user1, but cannot unmount /server1/users/user2. Now if user1 tries to login, would autofs automatically mount /server2/users/user1 for him or keep complaining about /server1/users/user1 not available (as the home dir has already been moved to server2 and not available in server1 any more)? Thanks, Prakash >>> Chris Croswhite <[EMAIL PROTECTED]> 11/29/05 6:44 PM >>> uhh, you mean you migrated it to a different server? Now you need to update the ldap maps, and force autofs to rehash all the maps (though it really does not do a rehash) on the client (autofs reload). You might want to first force umount of the changed dir or the old mount will stay. Also, you should hup nscd so that the entry is not cached. On Tue, 2005-11-29 at 15:30, Prakash Velayutham wrote: > Hi, > > What is the best practice when you want to move a user's home dir from > one server to another in an LDAP setting. Server1's /home/<user> is > mounted via NFS on the client's /server1/users mount point and server2's > /home/<user> is mounted via NFS on the client's /server2/users > mountpoint. The 2 are defined as separate map entries in the LDAP. How > do I go about migrating a user's home dir from server1 to server2 or > vice versa. > > Thanks for the help, > Prakash > > >>> Ian Kent <[EMAIL PROTECTED]> 11/27/05 4:49 AM >>> > On Sat, 26 Nov 2005, Prakash Velayutham wrote: > > > >>> Ian Kent <[EMAIL PROTECTED]> 11/25/05 1:47 PM >>> > > On Thu, 24 Nov 2005, Prakash Velayutham wrote: > > > > > Hi, > > > > > > I am new to this list, so please forgive my ignorances. > > > I had a SuSE Pro 9.0 system running autofs (v3) running earlier. The > > > > autofs itself did not have any issues at all until I decided to > > upgrade > > > the system to SuSE 9.3. It was a clean install, and autofs4-4.1.3 > > became > > > the default kernel autofs module. My autofs master map comes from a > > > OpenLDAP server and it contains 3 different mount maps. > > > /users (LDAP map) > > > /protein/users (LDAP map) > > > /import/users (LDAP map) > > > I also have a file-based map in this server (/export/users). > > > > > > Recently I was trying to move a user's home dir from server1 to > > server2. > > > After moving his home dir and making the relevant changes to his > LDAP > > > entry (homeDirectory attribute), I tried to restart autofs in the > > > above-mentioned server. The server already had several users logged > in > > > > > under /protein/users. Though the restart did not complain, I noticed > > > > that autofs status showed "Configured mount points" correctly and > > > removed the currently mounted mount points from "Active mount > points". > > > > > Is there a reason why? Also strangely the ownerships of the > previously > > > > > mounted dirs had been changed to root:root. > > > > I'm not sure what is not working or what has been broken. > > What is the actual problem and symptom? > > > > Ian > > > > Thanks Ian for a reply. What if I restart autofs when a user whose > home > > dir is mounted through autofs is already logged into the system (and > > hence at least one of the automount entries is being used)? What will > > the system do in that case? > > On runing "reload" it should, depending on version and patch levels > re-read and update the map, leave the mounted directory mounted and > leave > the stale map entry for cleanup next time the map is reloaded and the > entry isn't mounted. > > "Restart"ing is much more agressive and I wouldn't recommend it if you > have mount that are in use. To restart you really need to have nothing > actually in use. > > > > > And also if I change the ldap attribute "homeDirectory" for a user, do > I > > have to restart autofs in a system for that change to be seen. Because > I > > sometimes see that the system has cached the user's attributes from > LDAP > > and tries to use that and fails. > > autofs doesn't use that attribute so no, but you'll need to be sure that > > the automount map entry that is used to access that directory is still > valid following the change and if it also had to be changed then you > might > need to "reload" autofs. It's worth pointing out that later versions > (most > RedHat versions and 4.1.4 I think) of autofs should recognise this > change > on access without needing to re-load the map. > > The other thing I noticed about your query was the question about the > root > owned directory. At variuos times in the past development autofs has > been > (mostly intentionally) lazy about cleaning up mount point directories. > When autofs directories don't have a filesystem mounted on them they > will > appear root owned. It shouldn't make a difference to operation. > > Ian > > _______________________________________________ > autofs mailing list > [email protected] > http://linux.kernel.org/mailman/listinfo/autofs > > _______________________________________________ > autofs mailing list > [email protected] > http://linux.kernel.org/mailman/listinfo/autofs _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
