Thrum

What is opendirectoryd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

opendirectoryd is the macOS daemon that answers questions about users, groups and other account records, from the local database and from directory servers such as Active Directory or LDAP. It is busy when programs look up many accounts, when you log in, or when a network directory the Mac is bound to cannot be reached. It is part of macOS and must keep running.

opendirectoryd at a glance

opendirectoryd
Made byApple (part of macOS, Open Directory)
TypeSystem daemon
Location/usr/libexec/opendirectoryd
Runs asroot
Started bylaunchd job com.apple.opendirectoryd
Can you quit it?No. User, group and login lookups fail until launchd restarts it.

What is opendirectoryd?

Its man page calls it a launchd job "for client access to local or remote directory systems" and says Open Directory "forms the foundation of how Mac OS X accesses all authoritative configuration information (users, groups, mounts, managed desktop data, etc.)". Modules let it talk to Active Directory, LDAP, NIS and the local database, for authentication (password checks and changes), queries and record changes, and finding servers.

So whenever something on the Mac turns a user ID into a name, checks your password at login or unlock, or reads group membership, opendirectoryd answers. It runs as root from the com.apple.opendirectoryd launchd job.

Is opendirectoryd safe?

Yes. It is part of macOS in /usr/libexec on the read-only system volume. Logging in and many file operations depend on it.

Why does opendirectoryd use so much CPU, network and memory?

How much CPU is normal for opendirectoryd?

Near 0% CPU on a Mac with only local accounts, with blips at login and when apps look up accounts. Macs bound to a directory server see more activity, especially when the network changes.

How do you stop opendirectoryd from using so much CPU?

  1. Check for a network directory. Open System Settings > Users & Groups and look for Network account server. If the Mac is bound to a server, opendirectoryd contacts it.
  2. Connect to the directory's network. If the Mac is bound to Active Directory or LDAP and you are away from that network, connecting through your organization's VPN usually stops the retries.
  3. Flush the lookup cache. Run sudo dscacheutil -flushcache in Terminal if lookups return old information after an account change.
  4. Review directory settings. Directory Utility, in /System/Library/CoreServices/Applications, shows which directory services are configured and their search policy. Ask your administrator before changing them.

When should you worry about opendirectoryd?

Long delays at login together with high opendirectoryd CPU on a bound Mac usually mean the directory server cannot be reached. Contact your IT department rather than unbinding, which can stop network accounts from logging in.

Sustained high CPU on a Mac with only local accounts is unusual; find the program making lookups with log stream --process opendirectoryd.

How do you check opendirectoryd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type opendirectoryd in the search field. The CPU tab shows its % CPU. The Network tab shows its Sent Bytes and Rcvd Bytes. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every opendirectoryd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'opendirectoryd' | grep -v grep
nettop -p opendirectoryd

How can Thrum help with opendirectoryd?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when opendirectoryd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about opendirectoryd

What is Open Directory?

Apple's directory technology: a client API, a directory server and the opendirectoryd daemon, so that one interface can reach the local account database, Active Directory, LDAP and other directory systems.

How do I list local users from Terminal?

Run dscl . -list /Users. dscl talks to opendirectoryd to read the local directory.

Sources