Hey again Jon,
  1. First off...
    Originally Posted By: jchuzi
    Here we go:
    type -a locate{,.updatedb}
    locate is /usr/bin/locate
    /usr/bin/type: line 4: type: locate.updatedb: not found

    New info from macosxhints leads me to think we can get a better fix on this situation. Most likely, that type command failed to show the locate.updatedb executable simply because your shell's $PATH variable doesn't include the /usr/libexec folder.

    To confirm that theory, try this listing (please):

    ls -l /usr/libexec/loc*



  2. Next...
    Originally Posted By: jchuzi
    locate *[0-9][0-9][0-9].locate
    locate: No match.
    (Just as you said, Hal.)

    Did you not get some message as well? (i guess not)

    Reportedly, the weekly locate database building can be easily kicked off by the user. Apple has simply postponed its *initiation* by waiting until the user actually tries to use the locate command...

       locate test

       WARNING: The locate database (/var/db/locate.database) does not exist.
       To create the database, run the following command:

       sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.locate.plist

       Please be aware that the database can take some time to generate; once
       the database has been created, this message will no longer appear.


    ... at least that's what's supposed to happen (the first time), according to a macosxhints forum poster.

    I gather you never saw that message then[?].

    Not sure if you'd like to get that weekly task running or not... but before loading that plist, perhaps you could just read (and post) its content for us?

    To show us what it says and/or determine if it even exists, try this (please):

    defaults read /System/Library/LaunchDaemons/com.apple.locate

Thanks.

Last edited by Hal Itosis; 01/05/10 10:06 PM. Reason: fix last command by removing space