Directory Service - high CPU usage & network usage

I would also love to know what's going on, this is very frustrating.

Hi,

Some questions about the issue......
1. Have you configured the Directory services with any DNS servers?
2. How many processes you see in Activity monitor under All processes?
3. If you have configured the directory services, then you will need to check the traffic in the network.

Post all information that can be helpful and let me see whether I can help you.....

1. No
2. One
3. N/A

Try forcing it to quit...it will relaunch automatically, and see if it continues using up system resources.

What is that process by the way?
Check directory from Applications>Utility to see whether you have any directory services turned on accidentally.

Regards..

it relaunches, sleeps for a bit then ramps up the CPU usage again for a minute or 2 then idles, then ramps back up after a bit, etc.

I have LDAPv3 and AD turned off in Directory Utility.

More information: This is a new uMBP, my last MBP didn't have this problem on 10.5.7 (or at all, for that matter). Also, I re-installed Leopard after getting the new computer to get rid of languages, printer drivers, etc to save disk space.

Message was edited by: camflan

Process is "DirectoryService", running as root.

Message was edited by: camflan

I'm not sure if this is the best thing to do because it's specifically mentioned that doing it is for "extreme cases", but you could try flushing the directory services cache with the following command in the Terminal:

dscacheutil -flushcache

(you may need to use "sudo" before the command such as "sudo dscacheutil -flushcache")

Didn't help. I thought it might be iStat widget having issues connecting to the net -- no dice there either.

Considering trying to find a 10.5.0 DirectoryService binary to drop in there...apparently that fixed this problem for lots of people on 10.5.1 and 10.5.2

Hi,

I had been suffering this problem for a few weeks, and started taking a closer look at the "dscacheutil -statistics" output. I noticed that there were a high number of cache misses, and that even reloading the same web page did not find any cache hits, and thus external lookups were being done. Very strange.

I then remembered that I have a very large /etc/hosts file that is designed to block annoying advertisements on web pages, and which I had downloaded from some helpful site. The file was 54,674 lines long.

On a hunch I replaced this with the system default 4-line version, killed and restarted DirectoryServices, and the problem has disappeared!

So this might be something other people might try ...