Thrum

What is automountd, and why is it running on my Mac?

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

automountd is the daemon that mounts and unmounts network file systems on request from autofs, the kernel's automatic mount service. It runs when something accesses a path controlled by an automounter map, such as /home or /Network/Servers, and is otherwise idle. It is part of macOS and safe.

automountd at a glance

automountd
Made byApple (part of macOS, autofs)
TypeSystem daemon
Location/usr/libexec/automountd
Runs asroot
Started bylaunchd job com.apple.automountd
Can you quit it?Yes, but launchd starts it again the next time a path under an automounted folder is used.

What is automountd?

Its man page says automountd responds to requests from autofs to mount and unmount network file systems and to supply the contents of directories, based on automounter maps. launchd starts it on demand.

The maps are listed in /etc/auto_master. On a standard macOS 26 install that file sets up /home (from the auto_home map), /Network/Servers and static entries from /etc/fstab. Organizations that use network home folders or shared servers add their own maps.

Is automountd safe?

Yes. It is at /usr/libexec/automountd, runs as root, and is signed by Apple (com.apple.automountd).

Why does automountd use so much CPU and network?

How much CPU is normal for automountd?

On a Mac that does not use network home folders or automounted servers, automountd is usually not running or idle. Brief activity when a script or app touches /home or /Network is normal.

How do you stop automountd from using so much CPU?

  1. See what is mounted by autofs. Run mount | grep autofs in Terminal to see the automount triggers and any shares currently mounted.
  2. Check the maps. Open /etc/auto_master in a text viewer to see which folders are controlled by autofs on this Mac.
  3. Flush cached information. Run sudo automount -vc. The man page says -c tells automountd to flush any cached information, and -v prints what it does.
  4. Unmount idle shares. Run sudo automount -u to unmount all automounted file systems that are not busy.

When should you worry about automountd?

Look into it if automountd is busy constantly on a Mac that does not use network mounts. Some app or script may be scanning /home or /Network repeatedly.

An automountd outside /usr/libexec would not be Apple's.

How do you check automountd in Activity Monitor and Terminal?

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

In Terminal, the first command lists every automountd 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 'automountd' | grep -v grep
nettop -p automountd

How can Thrum help with automountd?

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 automountd 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 automountd

Why does my Mac have a /home folder?

/etc/auto_master maps /home to the auto_home map for network home folders. On most Macs it is an empty automount point.

Does automountd handle shares I connect to in Finder?

Shares you connect to with Go > Connect to Server are mounted directly, not through automounter maps. automountd handles paths listed in the maps.

Sources