This seems to work fine when installed from scratch into /usr/local : orca ~ # ls -l /etc/updatedb.conf lrwxrwxrwx 1 root root 28 Mar 10 14:16 /etc/updatedb.conf -> /usr/local/etc/updatedb.conf # stolen from RHEL5 orca ~ # cat /etc/updatedb.conf PRUNEFS="sysfs selinuxfs usbdevfs devpts nfsv4 nfs auto autofs afs sfs proc smbfs cifs iso9660 udf" PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /net /sfs /selinux /udev /mnt/floppy /media" # stolen from RHEL5 orca ~ # cat /etc/cron.daily/mlocate.cron #!/bin/sh nodevs=$(< /proc/filesystems awk '$1 == "nodev" { print $2 }') renice +19 -p $$ >/dev/null 2>&1 /usr/local/bin/updatedb -f "$nodevs" orca ~ # locate .mp3 locate: can not open `/usr/local/var/mlocate/mlocate.db': No such file or directory orca ~ # ls -l /usr/local/var/mlocate/ total 14440 -rw------- 1 root root 14766080 Mar 10 14:44 mlocate.db.8gNI7r ^ still building initial DB :)
Reassigning to maintainer, CCing base-system herd.
So using an entry in /etc/portage/package.keywords like sys-apps/mlocate ** did not work for you to install it via Portage and use the configuration and cron files shipped with the ebuild? Those are enhanced in comparison to the ones from RHEL.
will probably work, I'm going to wait until this updatedb is complete (currently cataloging ~5.5TB of files), then I'll backup the db, un-install mlocate in /usr/locate, and re-install via portage.
Went ahead and killed the mlocate process that was running from the previous install and installed mlocate from portage, moved the mlocate.db into /var/lib/mlocate from /usr/local/var/mlocate/. Locate seems to work and the new mlocate should have no problems merging changes into the mlocate.db from the previous instance in /usr/local .
keyworded ~arch for ppc64, closing
