Since upgrading to 10.2, I've had some issues with the automounted Home Directories of Mac OS X Server.
When we had 10.1 Server installed and 10.1 Client installed, the "Users" directory was automounted and users had access to their Home Directories. If you went to "Connect to Server" and chose the server, you would see the other shares, with the first one greyed out (because you've already mounted it). You could mount the others and eject them normally with no problems.
With 10.1 Server and 10.2 Client, the same automounting things happened and users could use their Home Directories. However, in Connect to Server, all of the shares were available and you could re-mount the "Users" share. If you ejected all the normal shares (ie, not the automounted one), the automounted one would go away too. This happened even if I didn't mount the "Users" share again and went with something else. Whenever the last share was ejected, my automounted share went away too.
I was hoping with my upgrade to 10.2 Server, this bug would be gone. I assumed it was an incompatibility issue between 10.1 Server and 10.2 Client. I was wrong. The same problem exists with 10.2 Server and 10.2 Client.
Has anyone else experienced this and if so, what have you done to work around it? The only solution I've found is to log out and log back in to re-mount the Home Directory. This is a pain and not something I want to have to explain to my users.
Thanks for your help.
-----------------UPDATE-----------------
It seems I was pre-mature in my assumption. Of course, I *just* posted that and then right after I found new information. Anyway, it seems the auto-mounted share isn't actually unmounted. It's still there and still works. Applications still know it and can write to it. The Finder is the app that loses track of it. If I relaunch the Finder, everything is normal. I guess it's another Finder bug. I'll be posting my feedback shortly.
Thanks anyway.
Top
