We have a new iMac on Snow Leopard authenticating against an OpenLDAP directory. Homes are on (automounted) NFSv3 (Linux, kernel-server).

NFS seems to work pretty well (if a bit slow, but we don't want to risk not using locking).

When a user logs in using an LDAP account, however, weird things happen: Sometimes the machine hangs even before all the Desktop icons had been initialized, sometimes the user can work for a little while, but after a while the machine starts hanging: New processes by the user don't get off the ground, old processes cannot be quit (even force quit hangs). Sometimes early on, sometimes later, the dock doesn't react at all (does not show context menu for programmes) and the Finder won't take focus.

All the same, even if everything else seems to hang, I can log in via SSH and at least cleanly reboot the machine. SSH login works even for LDAP users. If I disable LDAP, everything seems to work normal for local users.

We used the OpenLDAP directory with RFC 2307 mapping. We only really use it for account data, so I tried removing any mappings except the Person, User and Group mappings in the Directory Utility. Both mappings have the same resulting misbehaviour.

Edit: This seems to be the same problem as this gentleman has: Apple Forums 1/2

  • 1
    Are you sure this isn't an NFS problem? We saw this with our older NFS servers running kernel 2.6.13. It went away with a newer Linux NFS server. – Jeff Strunk Feb 28 '11 at 14:41
  • I'm not on that anymore, but yes, it may be that "no root squash" is mandatory for not locking up when using Macs with NFS. Version, I'm not so sure. – Bernd Haug Mar 2 '11 at 11:05
  • no_root_squash is not mandatory and not recommended. – Jeff Strunk Mar 2 '11 at 18:43

Mac applications store most of their configurations for each user under their home directory:


If I understand correctly, the users who auth against LDAP server will have a nfs home directory, right? In that case, it sounds the applications are hanging either because the Library doesn't exists or the configs are being regenerated and there are a lot of transmits, or the connection Is just over saturated. I suspect that if you were to either run nfsstat or tcpdump on the server, you will see a lot of traffic from that client.

There are a few things you can try:

  • used nfs4 if you haven't done so already, as there is significant performance improvements with that version. Unfortunately, it seems that nfs4 under Leopard is of alpha quality and I could not find whether it has improved significantly under Lion.

  • mount the home directory as disk share. Not optimal, but at least configs are not over the network.

-copy the Library directory over to the home directory of each user. Depending on the number of users, this may not be scalable and if the apps performs a lot of I/O, will not alleviate the problem.

  • put the iMac on the wired network rather on the wifi to reduce latency.

  • as mentioned earlier, enable "Create Mobile account at login"

  1. Your mac isn't connecting via wifi is it?

  2. I know this solution isn't for everyone, but do you have the Create Mobile account at login box checked? This is pretty necessary if you experience network blips, if your mac connects via wifi, or if you plan on taking your mac off-net ever.

I experienced a huge speed increase in our macs authing against AD after we started using "mobile" accounts.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.