autofs-4.1.3 not working properly
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
Quoted 1 line
Quoted 1 line
Quoted 1 line
Ian Kent <[email protected]> 11/27/05 4:49 AM >>>
Quoted 19 lines · Prakash Velayutham
Quoted 1 line
Quoted 1 line
Quoted 1 line
Ian Kent <[email protected]> 11/25/05 1:47 PM >>>
Quoted 6 lines · Prakash Velayutham
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. Theautofs itself did not have any issues at all until I decided to
upgrade
Quoted 1 line
the system to SuSE 9.3. It was a clean install, and autofs4-4.1.3
became
Quoted 7 lines
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).
Quoted 3 lines
Quoted 1 line
Recently I was trying to move a user's home dir from server1 to
server2.
Quoted 1 line
After moving his home dir and making the relevant changes to his
LDAP
Quoted 2 lines
Quoted 2 lines
entry (homeDirectory attribute), I tried to restart autofs in the above-mentioned server. The server already had several users logged
in
Quoted 5 lines
Quoted 5 lines
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".
Quoted 2 lines
Quoted 2 lines
Is there a reason why? Also strangely the ownerships of the
previously
Quoted 9 lines
Quoted 2 lines
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
Quoted 3 lines
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.
Quoted 2 lines
And also if I change the ldap attribute "homeDirectory" for a user, do
I
Quoted 1 line
have to restart autofs in a system for that change to be seen. Because
I
Quoted 1 line
sometimes see that the system has cached the user's attributes from
LDAP
Quoted 1 line
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