What is syslogd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, man page and /etc/asl.conf checked on macOS 26.3.1.
syslogd is the Apple System Log server: it receives log messages sent through the classic syslog and ASL interfaces and the kernel, and stores them in the ASL data store and files such as /var/log/system.log. It uses CPU and disk when programs send it many messages. It is part of macOS and should keep running.
syslogd at a glance
| syslogd | |
|---|---|
| Made by | Apple (part of macOS, Apple System Log) |
| Type | System daemon |
| Location | /usr/sbin/syslogd |
| Runs as | root |
| Started by | launchd job com.apple.syslogd |
| Can you quit it? | No. launchd restarts it, and messages sent to it meanwhile are lost. |
What is syslogd?
The man page says the syslogd server "receives and processes log messages. Several modules receive input messages through various channels, including UNIX domain sockets associated with the syslog(3), asl(3), and kernel printf APIs, and optionally on a UDP socket from network clients." Messages are kept in a data store and in files, and aslmanager cleans up old data.
Most of macOS now logs through the newer unified logging system run by logd, but syslogd still runs for software that uses the older interfaces. It runs as root from the com.apple.syslogd launchd job.
Is syslogd safe?
Yes. syslogd is part of macOS in /usr/sbin on the read-only system volume. It has built-in limits: the man page says user processes are limited to 36,000 messages per hour, and kernel messages to 500 per second per process by default.
Why does syslogd use so much CPU and disk?
- Programs using the classic syslog interface. Older and cross-platform software, such as some command-line tools and servers, logs through syslog. A program that logs heavily keeps syslogd busy.
- Writing system.log and the ASL store. Messages that match the rules in
/etc/asl.confare written to files such as/var/log/system.logand to the ASL store in/var/log/asl. - Duplicate messages. syslogd coalesces repeated identical messages in log files, which is a sign that one program is repeating itself.
How much CPU is normal for syslogd?
Near 0% CPU with occasional blips. On a typical Mac very little software uses syslog any more, so it is usually quiet.
How do you stop syslogd from using so much CPU?
- Look at system.log. Open Console, click system.log in the sidebar, and look for messages that repeat many times. Console needs an administrator account to show system reports.
- Identify the sender. Each line in
system.lognames the process that sent it. That process is the cause. - Fix or remove the sender. Update or quit the program, or turn off its verbose logging if it has such an option.
When should you worry about syslogd?
syslogd at high CPU for a long time means some program is flooding it; /var/log/system.log will show which.
A syslogd outside /usr/sbin would not be Apple's.
How do you check syslogd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type syslogd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every syslogd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'syslogd' | grep -v grep
sudo fs_usage -w -f filesys syslogd
How can Thrum help with syslogd?
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 syslogd 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 syslogd
Is system.log still used on macOS 26?
Yes. Console lists it as the legacy system log file at /private/var/log/system.log, but most macOS messages are now in the unified log instead.
Does syslogd accept messages from the network?
Its man page says it can optionally receive messages on a UDP socket from network clients. That is an option, not something a standard Mac setup uses.
Sources
- syslogd(8) man page: run man syslogd in Terminal
- Apple Support: Reports in Console on Mac