Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#5586 - mlocate's updatedb does not use /etc/updatedb.conf
Attached to Project:
Arch Linux
Opened by Viktor Peters (Mythoz) - Saturday, 14 October 2006, 11:11 GMT
Last edited by James Rayner (iphitus) - Monday, 09 April 2007, 00:11 GMT
Opened by Viktor Peters (Mythoz) - Saturday, 14 October 2006, 11:11 GMT
Last edited by James Rayner (iphitus) - Monday, 09 April 2007, 00:11 GMT
|
DetailsA short while ago I noticed that mlocate's updatedb does not respect the PRUNEPATHS in /etc/updatedb.conf. This is because it just do not use /etc/updatedb.conf! It expects the config file in /usr/etc/updatedb.conf.
$ strace -e trace=file -o '| grep updatedb.conf' updatedb open("/usr/etc/updatedb.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) Another strange behaviour is, that it uses /usr/var instead of /var. See also 'FILES' in updatedb manpage. Additional options for configure ('--sysconfdir=/etc --localstatedir=/var') should solve this issues. |
This task depends upon
Requested task be re-opened - All /usr/var paths must be updated to /var in PKGBUILD and mlocate.install, too!