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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To James Rayner (iphitus)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

A 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

Closed by  James Rayner (iphitus)
Monday, 09 April 2007, 00:11 GMT
Reason for closing:  Fixed
Comment by Roman Kyrylych (Romashka) - Wednesday, 21 March 2007, 11:53 GMT
Viktor Peters (Mythoz):
Requested task be re-opened - All /usr/var paths must be updated to /var in PKGBUILD and mlocate.install, too!
Comment by Andrew Fyfe (space-m0nkey) - Sunday, 08 April 2007, 22:28 GMT
Patch attached that cleans up the install
Comment by Andrew Fyfe (space-m0nkey) - Sunday, 08 April 2007, 22:29 GMT
Forgot the patch
   mlocate-PKGBUILD.patch (2.4 KiB)

Loading...