HeartbeatHocusFocusFilesMacHyperTile
Guide

opendirectoryd, the daemon that knows who everyone is

opendirectoryd is the Mac daemon behind every account and group lookup. Measured live: five million cached answers, the panic clause, and why its CPU moves.

By Chethan Kumar S N · Updated

Every series like this one has a daemon that turns out to be load bearing. You open Activity Monitor expecting a list of gnats and find a column member with a corner office. opendirectoryd is that one here. It is the process standing between you and your own desktop every single morning, because the login screen does not know who you are. It asks.

The name decodes plainly. Open Directory is Apple’s name for its account and directory technology, and the d is the daemon suffix this whole series runs on. The daemon’s job is to be the single place the rest of the system goes with identity questions: which user is uid 501, is that user in the admin group, what groups does everyone belong to, does this password open this account. File permissions, sudo, login, screen sharing, App Store receipts, all of it eventually becomes a question put to this one process.

This page is built like the other process pages in the series, from the daemon’s own manual entry, its own launch configuration, its own statistics tool and one hour of its own logs, measured read only on one Mac running macOS 27.0.1 on Apple silicon with 27 days of uptime. Every command is at the end. None of them changes anything.

opendirectoryd(8) is 3,435 bytes, and unlike most of its colleagues it is not one sentence long. It reads like the constitution of a small country:

opendirectoryd is a launchd(8) job which replaced "DirectoryService"
as a core part of the Open Directory technology. Several modules
are provided that allow access to existing directory systems:

    o   Active Directory
    o   LDAP
    o   Local Database

The replacement happened back in the Snow Leopard era, when DirectoryService retired, which itself had replaced the even older NetInfo before that. The man page then says the sentence that explains why this daemon never gets to sleep:

Open Directory forms the foundation of how macOS accesses all
authoritative configuration information (users, groups, mounts,
managed desktop data, etc.).

Authoritative is the word doing the work. Lots of things on a Mac cache or guess at identity. This is the record of truth, and everything else is a downstream copy.

Root, never exits, and the clause about panicking

The identity card for the daemon on the measured Mac:

$ ps -Awwo pid,ppid,user,%cpu,rss,etime,args | grep "[/]opendirectoryd"
452     1 root       1.8  16304 27-20:13:00 /usr/libexec/opendirectoryd

Parent 1, so launchd started it. User root, because the account database belongs to the machine, not to you. The etime column equals the Mac’s entire uptime, and launchctl agrees: runs = 1, never exited, state running since boot. The binary is 3.3 MB at /usr/libexec/opendirectoryd, built for Intel and Apple silicon together, signed by Apple on 9 August 2026, hardened runtime flag set.

Its launch configuration, /System/Library/LaunchDaemons/com.apple.opendirectoryd.plist, has KeepAlive set, seven Mach services on the door, and one clause nobody expects to find in a plist:

Key in the plistWhat it means
KeepAlive = trueif it dies, launchd restarts it immediately
PanicOnConsecutiveCrash = truetwo crashes in a row are treated as a system emergency
osWatchdog Mach servicea watchdog endpoint, so someone can check it is alive
com.apple.system.DirectoryService.libinfo_v1the kernel’s door, for identity lookups
com.apple.system.DirectoryService.membership_v1the kernel’s second door, for group checks
BeginTransactionAtShutdown = trueit closes its books cleanly on shutdown

That second row deserves a slow read. The panic clause is real, and its plain reading is: Apple would rather the whole Mac stop than keep running with a broken account database. A login system that half works is worse than one that visibly fails. When people ask in forums whether it is safe to force quit this daemon, the plist has already answered the opposite question.

The heaviest quiet daemon in the series

Here is the number that surprises. Over 27 days and 20 hours of uptime, opendirectoryd accumulated 517 minutes and 18 seconds of processor time. That is about nineteen minutes a day, or 1.3 percent of one core, every day, while looking almost idle in any snapshot. For scale against the daemons measured earlier in this series:

DaemonProcessor time per dayShare of one core
opendirectorydabout 19 minutes1.3 percent
logdabout 9 minutes0.6 percent
fseventsdabout 5 minutes0.4 percent
apsd, usernoted, contactsd30 to 40 secondsunder 0.05 percent
routined16 seconds0.01 percent

logd was the previous titleholder in this series, the funnel everything shouts into. opendirectoryd doubles it. And the reason is not that the daemon is heavy. It is that everyone else is asking it things, constantly, all day, one microsecond at a time.

Just under five million answers

The daemon ships its own statistics tool, odutil, and its counters are the best evidence on this page. Across those 27 days:

CounterCache hitsCache misses
Translation, userland4,022,1182
Translation, kernel242,3059
Membership checks, kernel91,256498
Group list requests641,0601,631

Translation means turning an identifier into a person: a uid number into a username, or a UUID into an account. Membership means the is this user in that group question that every file permission check asks. Group list is what the command id prints, the full set of groups an account belongs to. The measured Mac’s own list runs seventeen groups deep, from staff and admin to com.apple.access_ssh, and each line of it was served here.

Total it and the daemon answered just under five million questions in under four weeks, roughly one hundred and eighty thousand a day. The hit rates are the story: 4,022,118 hits against 2 misses in userland translations is a miss rate so small it rounds to nothing. The latency histogram puts almost every hit in the one microsecond bucket. This is a daemon that has done its job so many times the answers live in cache, one millionth of a second away.

The kernel half explains the plumbing. The counters named kernel are answered from a cache the kernel keeps, fed by opendirectoryd through those DirectoryService Mach services in the table above. The kernel is a demanding client: it needs to know file ownership on every operation and cannot wait for a daemon round trip, so opendirectoryd keeps the kernel’s copy current and the counters count both sides.

One hour of its unified log, 393 lines, reads the same way. Line after line of kauth_membership_check and kauth_map_identifier, the kernel cashing in cache, and the occasional honest miss logged as getservbyname failed with result Not Found. There is no drama in this log. The lookups themselves run at about a hundred and twenty five a minute, nearly all answered from cache without a line ever being written, and what the log catches is the refill work, a line every nine seconds on average, for a month.

Who keeps it busy

odutil show nodes prints the daemon’s live client roster, and it is the closest thing to a cast list for this page:

453  -- apsd -- total (3)
460  -- locationd -- total (1)
479  -- corebrightnessd -- total (3)
498  -- loginwindow -- total (3)
579  -- systemstatusd -- total (1)
707  -- com.crowdstrike.falcon.Agent -- total (1)
973  -- coreauthd -- total (1)
1047 -- identityservicesd -- total (3)

loginwindow needs no explanation: it is the login screen, and every unlock is a burst of lookups. coreauthd and identityservicesd handle authentication and Apple Account identity. apsd shows up because push notification routing knows about accounts. And the CrowdStrike agent is there because third party security software lives and dies by asking who owns which process, which is exactly this daemon’s department. Every client holds references to two nodes, /Local/Default and /Search. The first is the local database. The second is the search path, the ordered list of places to look, which on a home Mac is one entry long.

There is independent confirmation that this daemon works hard, from an unlikely witness. The logd page in this series dug into logd’s own rollover receipts, the records of who filled the logging buffer, and the largest rollover on that Mac laid 15.4 percent of one batch at opendirectoryd’s door, second only to a simulator rendering service. The account daemon does not just answer questions. It talks about answering them, enough to be one of the system’s chattiest processes. A build running, a simulator booting, a backup tool walking every file’s owner: those are the storms, and logd’s receipts are where the receipts end up.

The database it serves

The truth lives in /var/db/dslocal/nodes/Default, a folder of property list files arranged as users and groups, one file per account. It is guarded ground: on the measured Mac, an ordinary user cannot even list the folder, because user records carry password material alongside the harmless fields. The daemon stands in front of it, and answers questions instead of handing out files.

You can watch that happen from the outside with two read only commands. Ask the daemon directly:

$ dscacheutil -q user -a name yourname
name: yourname
password: ********
uid: 501
gid: 20
dir: /Users/you
shell: /bin/zsh
gecos: Your Full Name

That is a live answer from the daemon’s cache, the same path every app’s lookup takes. And list the database through the official front door:

$ dscl . -list /Users
_accessoryupdater
_amavisd
_analyticsd
...

One hundred and thirty three records on the measured Mac, the large majority of them the underscore service accounts that other daemons in this series run as. When the netbiosd and contactsd pages mentioned reserved accounts like _netbios, this is the folder those names live in. opendirectoryd is the clerk of that cabinet.

The nodes you never configured

odutil show nodenames prints something that alarms people the first time they see it:

/Active Directory    Online
/Configure           Online
/Contacts            Online
/LDAPv3              Online
/Local               Online
/Local/Default       Online

Active Directory, on a home Mac that has never met a company network. It is not a connection. Those are registered module slots, present on every Mac, the man page’s module list turned into live node names. Online means the slot answers, not that a server is bound. The honest check for whether a Mac is actually joined to a network directory is Directory Utility, the GUI that configures exactly this daemon, hiding in System, Library, CoreServices, Applications, next to Keychain Access, on every Mac and in no Dock.

The one live oddity is /Contacts carrying four references, which sounds like it belongs to the contactsd page. It nearly does: it is the directory node through which contact lookups run, another client of the same cabinet.

The crash question, answered by its absence

The suggest completions for this daemon include experienced a problem, the phrasing of a macOS problem report dialog, so the question is fair. The measured answer: no opendirectoryd crash report exists on this Mac, in the user folder or the system one, across weeks of this series running. Remember the plist clause from earlier. PanicOnConsecutiveCrash, set true, means the engineering position is that this daemon failing twice in a row should stop the machine. A daemon that must not crash, mostly does not.

When the dialog does appear on a real Mac, the report to read is in Console under Diagnostic Reports, and the company network case is the classic one: a Mac bound to Active Directory whose server went away, so every lookup times out while the module waits. The fix is in Directory Utility, unbinding the dead node. Killing the daemon itself is not a fix that exists. KeepAlive brings it back in the same second, with the same question still queued.

What Apple says

Nothing, and that is verified, not assumed. The macOS User Guide’s complete table of contents, fetched for this page, contains the word directory zero times. Apple’s consumer documentation describes logging in, accounts and permissions endlessly, and never names the machinery, which by now is the established pattern of this whole series. The documentation that does discuss Open Directory in depth is the deployment material aimed at people running fleets of bound Macs. For everyone else, the daemon is at /usr/libexec/opendirectoryd, signed by Apple, and the sum of what you need to configure on a home Mac is nothing at all.

Three daemons, three meanings of who

The series has now covered three daemons whose territory is people, and the borders between them hold:

opendirectoryd knows accounts. Uid numbers, groups, login records, the question of who owns what, answered five million times from cache. contactsd knows the address book, the Contacts app’s data, served to apps that look a person up. trustd knows certificates, the cryptographic question of whether to believe a claim, and it evaluates trust, not identity. A Mac asks all three about the same human in different words, and none of them answers for the others.

A daemon that runs as root, never exits, would rather stop the machine than run broken, keeps the kernel’s copy of its own answers current, and spends nineteen minutes a day being the only thing on the Mac that knows who everyone is. Of everything measured in this series, this is the one that most deserves the word foundation.

See for yourself

Every claim above came from commands like these, all read only:

$ ps -Awwo pid,ppid,user,%cpu,rss,etime,args | grep "[/]opendirectoryd"
$ man opendirectoryd
$ plutil -p /System/Library/LaunchDaemons/com.apple.opendirectoryd.plist
$ launchctl print system/com.apple.opendirectoryd | grep -E "state|runs|minimum runtime"
$ odutil show statistics
$ odutil show nodes
$ odutil show nodenames
$ dscacheutil -q user -a name yourname
$ dscl . -list /Users | head
$ log show --last 1h --predicate 'process == "opendirectoryd"' --style compact
$ ls ~/Library/Logs/DiagnosticReports | grep -i opendirectory

The counters reset at reboot, so odutil show statistics always tells you about the current boot only. The latency histograms next to each counter are the nicest detail: print them on a Mac that has been up a while and you will find the one microsecond bar full and almost everything else empty, which is what a very good cache looks like.

Questions

What is opendirectoryd on Mac?

It is the daemon that runs the Mac's account database. Its own manual page describes it as a launchd job that gives the rest of the system access to local or remote directory systems, and it replaced an older daemon called DirectoryService as the core of Apple's Open Directory technology. In practice that means three things. It holds the list of users and groups on the Mac, including the hundred plus underscore service accounts. It answers every is this user in that group question that file permissions generate. And if the Mac is bound to a company network it fronts the Active Directory or LDAP servers too. It runs as root, it starts at boot, and on the Mac measured here it has never exited once.

Why is opendirectoryd using so much CPU?

Because the whole system asks it questions all day. On the Mac measured here it answered just under five million lookups in twenty seven days, about one hundred and eighty thousand a day, and it burned roughly nineteen minutes of processor time a day doing it, about 1.3 percent of one core. That makes it the heaviest quiet background daemon measured in this series, more than double logd. Nearly every answer came from cache in about a microsecond, so the cost is the sheer number of questions, not any one of them. If it runs genuinely hot for hours, the daemon is the messenger: look for the client storm, with log stats or odutil show requests, not for a fault in the daemon.

opendirectoryd experienced a problem, what happened?

On the Mac measured here, zero crash reports, in either the user or the system DiagnosticReports folders, across the whole series of measurements. That is close to by design. The daemon's own launch configuration contains a clause named PanicOnConsecutiveCrash, set to true, which tells the system that two crashes back to back are an emergency worth stopping the whole machine for. Apple has effectively decided that a Mac whose account database daemon is failing should not keep running half working. So the dialog is rare. When it does appear, read the report in Console under Diagnostic Reports. On company Macs bound to a directory server, the classic cause is the server going away, not the daemon.

What is odutil, and what does it show?

odutil is the daemon's own command line tool, sitting in usr sbin, and its read only half is odutil show. odutil show statistics prints the lookup counters quoted on this page, cache hits and misses with latency histograms. odutil show nodes prints who is connected right now: on the measured Mac that list included loginwindow, apsd, locationd, corebrightnessd, coreauthd, identityservicesd, and a third party security agent, each holding references to the local database node. odutil show nodenames lists the configured directory nodes, from /Local/Default to /Active Directory. There is also dscacheutil, whose -q flag asks the daemon a question directly and prints the answer, which is the fastest way to watch it work.

What is the difference between opendirectoryd, contactsd and securityd?

Three daemons, three different words for people. opendirectoryd knows accounts: the uid numbers, the groups, the login records, the question of which user owns what. contactsd knows the address book: the names and numbers inside the Contacts app, served to apps that look a person up. securityd knows secrets: keys and certificates in the keychain, and the cryptographic verdicts other daemons ask it for. A quick test from Activity Monitor: opendirectoryd runs as root and never exits, contactsd runs as your user and comes and goes, securityd runs as root and is busiest when something is unlocking or verifying. The paths also tell the story, in libexec for the first and third, and inside the Contacts framework folder for the second.

Ready? Buy Ribbon for $15, or read all the guides.