FS#4123 - updatedb does not honor /etc/updatedb.conf

Attached to Project: Arch Linux
Opened by Jens Adam (byte) - Tuesday, 07 March 2006, 20:25 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 08 April 2007, 08:07 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

updatedb always indexes the entire /-tree, no matter what PRUNE{FS,PATHS} is set to. I discovered this when my external hdd was attached and the daily cron job started. It should have never descended into /media or /mnt. Tried again with the default updatedb.conf, tried with "export PRUNE{FS,PATHS}"(as per Slackware, no problem there) ... to no avail.

Confirmation, anyone?
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 08 April 2007, 08:07 GMT
Reason for closing:  Not a bug
Comment by Jürgen Hötzel (juergen) - Wednesday, 08 March 2006, 09:56 GMT
Please attach your "/etc/updatedb.conf"

Jürgen
Comment by Jens Adam (byte) - Wednesday, 08 March 2006, 11:50 GMT
Hey, got it: slocate doesn't care about #!
If I just change the original lines without commenting/duplicating them, everything works fine.

What a stupid parser...
(application/octet-stream)    updatedb.conf-byte (0.3 KiB)
Comment by Jens Adam (byte) - Thursday, 16 March 2006, 01:56 GMT
I've confirmed the issue with the recent slocate 3.1 and noticed that the commandline options aren't very smart, too. I shall mail the maintainer and wait...
Comment by Roman Kyrylych (Romashka) - Saturday, 07 April 2007, 16:48 GMT
status?
Comment by Jens Adam (byte) - Sunday, 08 April 2007, 07:56 GMT
invalid, not a bug, won't fix, none... pick one ;)

Loading...