Benches macOS

5

"nobody" account

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I was doing some web surfing on my mac when I noticed the system slow down. I opened up Activity Monitor and noticed that the user account "nobody" was running a "find' command which was taxing the processor. Is this normal? I checked the crontab for my account, the root account, and the nobody account and all were empty. I seem to recall reading that OSX uses a different scheduler anyway. I also commented out the nobody user from /etc/passwd out of fear.

I only recently got internet access and have been running without a router/NAT, but do have the built-in firewall enabled. I do know better, but thought it would be safe until my Airport Extreme arrives (on Monday). Does it sound like my system has been compromised?

Thanks

5 replies

Sign in or join Beachball Help to reply.

  1. 0

    bdkjones

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi CCunning,

    The "nobody" user is perfectly normal; it's one of the five accounts created by OS X. Your Mac has not been compromised.

    For more information, see this article:

    http://developer.apple.com/internet/security/securityintro.html

  2. 0

    ccunning

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks. I feel a bit better. Do you know what the account is used for or why it would be pegging the processor with a "find" command?

  3. 0

    Charles Minow

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm guessing it might be Spotlight. I have a spotlight process running as "
    nobody" on my iMac. I also have a USB thing-a-ma-bob running as
    nobody:

    <pre class="command">/System/Library/PrivateFrameworks/MobileDevice.framework/Versio ns/A/Resources/usbmuxd -launchd</pre>

    As for the scheduled maintenance scripts, they're run by
    launchd. Their plists are in
    /System/Library/LaunchDaemons, and can be read like so:

    <pre class="command">defaults read /System/Library/LaunchDaemons/com.apple.periodic-daily</pre>

    <pre class="command">defaults read /System/Library/LaunchDaemons/com.apple.periodic-weekly</pre>

    <pre class="command">defaults read /System/Library/LaunchDaemons/com.apple.periodic-monthly</pre>

    The actual scripts themselves are in the
    daily,
    weekly, and
    monthly directories in
    /etc/periodic. The weekly one uses the
    find command, so it's possible it's that one. If your computer is asleep when the periodic script is supposed to run, it'll run later when it's awake, offset by however long your computer was asleep.

    I would definitely undo the change you made to
    /etc/passwd, as you'd want that user to be enabled for other reasons. As for safety until you get your Airport Extreme, just make sure no services (like File sharing, etc., are turned on, and most importantly, have a good password on your accounts.
    All of them).

    charlie

  4. 0

    bdkjones

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi CCunning,

    Basically, OS X creates the "nobody" account so that it has an account with very low permissions to carry out some basic tasks.

    The biggest thing that "nobody" handles is a process called "mdimport" which has to do with indexing metadata for Spotlight. It's possible that Spotlight was indexing your drive when you experienced the slowdown you mentioned.

  5. 0

    Király

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I betcha your weekly periodic task kicked in. I just ran mine manually by typing this Terminal command:

    sudo periodic weekly

    Right away the user
    nobody was running the find command and using up a lot of CPU.

    This is normal OS X behaviour, so don't worry about it!