find - sort - locate.big...

  • Time to time, while I am working on XCode,
    I hear a disk activity, so I launch the Terminal and type "top"
    and I see that the "find" command is taking 86% of the CPU. Then the command
    "sort", then the command "located.big" , then "located.cod".

    Do you know what's that? Is it a normal activity or could it be dangerous
    for my code?

    Best Regards
    --
    Lorenzo
    email: <archidea...>
  • Lorenzo wrete :

    > Time to time, while I am working on XCode,
    > I hear a disk activity, so I launch the Terminal and type "top"
    > and I see that the "find" command is taking 86% of the CPU. Then
    > the command
    > "sort", then the command "located.big" , then "located.cod".

    I think it's because of the weekly cleanup task of the system. Each
    week the system reconstruct the locate database (for use with the
    command "locate"), which is very disk/cpu consuming.

    --
    Damien Bobillot
  • I noticed the same thing - and to make it really a laugh the user was
    listed as "nobody". if its an apple app doing that then someone at
    apple has a sense of humor...  I was thinking it might be some sort of
    virus... why would nobody be running such an intense search of my hard
    drive?

    On May 13, 2006, at 7:35 AM, Lorenzo wrote:

    > Time to time, while I am working on XCode,
    > I hear a disk activity, so I launch the Terminal and type "top"
    > and I see that the "find" command is taking 86% of the CPU. Then the
    > command
    > "sort", then the command "located.big" , then "located.cod".
    >
    > Do you know what's that? Is it a normal activity or could it be
    > dangerous
    > for my code?
    >
    >
    > Best Regards
    > --
    > Lorenzo
    > email: <archidea...>
    >
    > _______________________________________________
    > Do not post admin requests to the list. They will be ignored.
    > Cocoa-dev mailing list      (<Cocoa-dev...>)
    > Help/Unsubscribe/Update your Subscription:
    > http://lists.apple.com/mailman/options/cocoa-dev/
    > <lgiese...>
    >
    > This email sent to <lgiese...>
    >
  • Thanks for clarifying that Kay... ;)  now I don't have to reload the
    system, call interpol. etc.
    Must be xcode building a symbol cache or something like that.

    On May 14, 2006, at 6:47 AM, Kay Roepke wrote:

    >
    > On 14. May 2006, at 6:03 Uhr, Lon Giese wrote:
    >
    >> I noticed the same thing - and to make it really a laugh the user was
    >> listed as "nobody". if its an apple app doing that then someone at
    >> apple has a sense of humor...  I was thinking it might be some sort
    >> of virus... why would nobody be running such an intense search of my
    >> hard drive?
    >
    > 'nobody' in UNIX-systems is normally used to run programs that should
    > not be able to write to any important system or user data. A security
    > thing. :)
    > Sorry, but there's no humor involved...
    >
    > -k
    >
  • On May 13, 2006, at 7:35 AM, Lorenzo wrote:
    > Time to time, while I am working on XCode,
    > I hear a disk activity, so I launch the Terminal and type "top"
    > and I see that the "find" command is taking 86% of the CPU. Then
    > the command
    > "sort", then the command "located.big" , then "located.cod".
    >
    > Do you know what's that? Is it a normal activity or could it be
    > dangerous
    > for my code?

    It is the locate database being rebuilt/updated.  By running as user
    nobody, the commands have minimal access to security critical areas
    of the system.

    See 'man locate'.

    x-man-page://locate

    b.bum