Opened 8 years ago
Closed 8 years ago
#53736 closed defect (duplicate)
slocate updatedb.conf PRUNEPATHS does not Prune
Reported by: | rsauve | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.1 |
Keywords: | slocate updatedb.conf | Cc: | |
Port: | slocate |
Description
I am running an old Apple Power Mac G5 with MacPorts version 2.4.1.
I installed port "Secure Locate 3.1 - Released March 7, 2006"
I have added one line in the updatedb.conf file in path /opt/local/etc/: PRUNEPATHS="/Volumes/Mac-Backup /Volumes/Data-Backup /tmp /private/tmp"
To update the slocate database I run the following command: sudo /opt/local/bin/slocate -u -c /opt/local/etc/updatedb.conf
However, slocate ignores PRUNEPATHS in updatedb.conf.
Here is an example:
roberts-power-mac-g5:~ robert$ ls /tmp . com.hp.launchport launch-Sx1bOr launchd-395.Fg6U5B .. launch-QyRnb3 launch-WjqTJg roberts-power-mac-g5:~ robert$ roberts-power-mac-g5:~ robert$ slocate launch-Sx1bOr /private/tmp/launch-Sx1bOr /private/tmp/launch-Sx1bOr/Listeners
I search for launch-Sx1bOr in /tmp, slocate shows it found in /private/tmp/ which path is in PRUNEPATHS.
I have also tested with my external hard drive attached, paths: /Volumes/Mac-Backup /Volumes/Data-Backup. Slocate updates /Volumes/Mac-Backup /Volumes/Data-Backup which is in PRUNEPATHS.
I have had a search on the net but there is very little information available. Is this a bug or a mis-configuration of the updatedb.conf?
Change History (1)
comment:1 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Resolution: | → duplicate |
---|---|
Status: | new → closed |