Skip to contentSkip to conversation

autofs-4.1.3 not working properly

DISCUSSION Prakash Velayutham 1 participant 1 message Nov 26, 2005 Kernel automounter

lore
Share & tools
lore
#0 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line

Ian Kent <[email protected]> 11/25/05 1:47 PM >>>

Quoted 5 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. The autofs 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 8 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).

Recently I was trying to move a user's home dir from server1 to

server2.

Quoted 11 lines

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?

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.

Prakash