Aplications/Locate/UPDATEDB_PRUNEPATHS Doesn't
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've discovered that adding '/windows' to the UPDATEDB_PRUNEPATHS variable through the YaST Editor for Sysconfig Files has no effect on the contents of the output of locate. IOW, after I change the setting and run updatedb as root, I still get a listing of what's under /windows. This is the variable in /etc/sysconfig/locate: UPDATEDB_PRUNEPATHS="/mnt /cdrom /tmp /usr/tmp /var/tmp /var/spool /proc /media /windows" Am I wrong to think this will prevent /windows from being added to the database? Do I need to blow away the database and start over? That is, are these old entries which haven't been removed? STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD4DBQFAO/0QH2SF0i7rrGwRAo/oAJ0bEw1O5rJbq6pP6YW/jeCUbTHG1wCTBwcf IBP4bePU9G75j9flpdgm+g== =tnZv -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 24 February 2004 08:40 pm, Steven T. Hatton wrote:
I've discovered that adding '/windows' to the UPDATEDB_PRUNEPATHS variable through the YaST Editor for Sysconfig Files has no effect on the contents of the output of locate. IOW, after I change the setting and run updatedb as root, I still get a listing of what's under /windows.
This is the variable in /etc/sysconfig/locate:
UPDATEDB_PRUNEPATHS="/mnt /cdrom /tmp /usr/tmp /var/tmp /var/spool /proc /media /windows"
Am I wrong to think this will prevent /windows from being added to the database? Do I need to blow away the database and start over? That is, are these old entries which haven't been removed?
STH
I should have added that the cronjob also ignores my settings. I'm not sure what to expect when running updatedb from the commandline. I tried explicitly sourcing the /etc/sysconfig/locate and exporting the UPDATEDB_PRUNEPATHS then running updatedb --prunepaths="$UPDATEDB_PRUNEPATHS". That worked as I would expect. /windows no longer shows in the update listing. So please allow me to refine my question. Should adding /windows to the Aplications/Locate/UPDATEDB_PRUNEPATHS list cause the cronjob that rebuilds the locatedb to exclude && remove /windows from the database? It doesn't seem to work like that. Is it broken, or am I screwing up? STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAPAn0H2SF0i7rrGwRAjqzAKCMl0X9jic4YPn/0kbKPcjJo/3KgACgq7Mv 0VQANRBMWkAq/rQO/1o/sD4= =WQ1n -----END PGP SIGNATURE-----
The Tuesday 2004-02-24 at 20:40 -0500, Steven T. Hatton wrote:
I've discovered that adding '/windows' to the UPDATEDB_PRUNEPATHS variable through the YaST Editor for Sysconfig Files has no effect on the contents of the output of locate. IOW, after I change the setting and run updatedb as root, I still get a listing of what's under /windows.
Of course. Those variables are only used by the cron task that runs updatedb daily - if you issue the command "updatedb" as root, it runs without parameters and will search all mounted disks accessible to root. -- Cheers, Carlos Robinson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 24 February 2004 10:43 pm, Carlos E. R. wrote:
The Tuesday 2004-02-24 at 20:40 -0500, Steven T. Hatton wrote:
I've discovered that adding '/windows' to the UPDATEDB_PRUNEPATHS variable through the YaST Editor for Sysconfig Files has no effect on the contents of the output of locate. IOW, after I change the setting and run updatedb as root, I still get a listing of what's under /windows.
Of course. Those variables are only used by the cron task that runs updatedb daily - if you issue the command "updatedb" as root, it runs without parameters and will search all mounted disks accessible to root.
I should have been more clear, as you may have noticed in my follow up. It also fails to prune in the cron job. I'll see what happens tonight after changing from /windows/F to /windows. I wonder how I can get updatedb to run the same way the cron job does. I guess I need to dig through the scripts. I often want to update the locatedb after doing a major cvs checkout, or similar. I'd like it to behave the same way as the cron job does. (assuming the cron job does the right thing.)
-- Cheers, Carlos Robinson
STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAPCinH2SF0i7rrGwRAjOpAKCVgkYqWLBIVFuCzj9N91eCa/TREQCggCy5 OK0Aer4I240ek335oFiCyrw= =eCKt -----END PGP SIGNATURE-----
On Tuesday 24 February 2004 11:46 pm, Steven T. Hatton wrote:
On Tuesday 24 February 2004 10:43 pm, Carlos E. R. wrote:
The Tuesday 2004-02-24 at 20:40 -0500, Steven T. Hatton wrote:
I've discovered that adding '/windows' to the UPDATEDB_PRUNEPATHS variable through the YaST Editor for Sysconfig Files has no effect on the contents of the output of locate. IOW, after I change the setting and run updatedb as root, I still get a listing of what's under /windows.
Of course. Those variables are only used by the cron task that runs updatedb daily - if you issue the command "updatedb" as root, it runs without parameters and will search all mounted disks accessible to root.
I should have been more clear, as you may have noticed in my follow up. It also fails to prune in the cron job. I'll see what happens tonight after changing from /windows/F to /windows. I wonder how I can get updatedb to run the same way the cron job does. I guess I need to dig through the scripts. I often want to update the locatedb after doing a major cvs checkout, or similar. I'd like it to behave the same way as the cron job does. (assuming the cron job does the right thing.)
updatedb --prunepaths='/mnt /tmp <etc>'
-- Cheers, Carlos Robinson
STH
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 02/25/04 07:41 + +----------------------------------------------------------------------------+ "`It can't happen here' is Number 1 on the list of famous last words." - David Crosby, rock singer and musician
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 25 February 2004 07:42 am, Bruce Marshall wrote:
updatedb --prunepaths='/mnt /tmp <etc>'
I meant without entering it all on the commandline. This does it: /etc/cron.daily/updatedb BTW, I think I figured out that it was never really broken, I just didn't realize I had been updating without arguments. I thought I was running the script that update runs rather than the raw command. Some returns don't show the windows directory. When the db was pruned, I didn't notice, When I broke it, I didn't realize it.
--+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 02/25/04 STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFAPNWCH2SF0i7rrGwRAtOGAJ9BnNR0yQpE206x7oziB3PjK95m3gCfejKi e8TTbFXYDMSsSEFbVU1r+BA= =TaOn -----END PGP SIGNATURE-----
participants (3)
-
Bruce Marshall
-
Carlos E. R.
-
Steven T. Hatton