Date: Mon, 1 Apr 1996 11:29:49 +0200 (MET DST) From: Wolfram Schneider <wosch@cs.tu-berlin.de> To: Thomas Gellekum <thomas@ghpc8.ihf.rwth-aachen.de> Cc: mpp@freefall.freebsd.org (Mike Pritchard), freebsd-hackers@freefall.freebsd.org Subject: Re: locate Message-ID: <199604010929.LAA00543@caramba.cs.tu-berlin.de> In-Reply-To: <199604010815.KAA21390@ghpc6.ihf.rwth-aachen.de> References: <199604010600.WAA01868@freefall.freebsd.org> <199604010815.KAA21390@ghpc6.ihf.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Gellekum writes: >Mike Pritchard wrote: >> What do people think of the idea of changing locate & its database >> update script to keep a list of ALL files on the system, and >> not just those that can been seen by the world. > >No, please. If the owner doesn't want to expose his files to the >world, locate should respect this. Agreed. At my university I start the locate service for private home directories with following find options: gfind /home/all \( -name prv -prune \) -or \( -name privat -prune \) -or \( -name private -prune \) -or \( -name Mail -prune \) -or \( -name mail -prune \) -or -print The whole locate database is now 16MB big ;-) >I'd prefer a new option to locate which gives the name of (an) >alternate database(s), so you could run locate for yourself. This >could also be used to locate files on NFS-mounted filesystems. Done (still not in -current). Wolfram
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604010929.LAA00543>