Date: Wed, 17 Oct 2007 12:51:40 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Stefan Esser <se@FreeBSD.org> Cc: cvs-src@FreeBSD.org, Ceri Davies <ceri@submonkey.net>, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/locate/locate updatedb.sh Message-ID: <20071017125140.GA464@FreeBSD.org> In-Reply-To: <4715F353.1070703@FreeBSD.org> References: <200710152209.l9FM9Jv3017150@repoman.freebsd.org> <20071016102013.GE23043@submonkey.net> <4714F06B.7070702@FreeBSD.org> <20071017103509.GA71990@FreeBSD.org> <4715F353.1070703@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Circa Oct 17 2007, Stefan Esser wrote: > Yes, I considered this. In fact, if there is consensus that FAT should > be excluded, I'd add another category to the configuration parameters > of the locate.updatedb script. Currently there is: > > $SEARCHPATHS (start points for the directory scan) > $PRUNEPATHS (sub-trees to exclude from scanning) > > $FILESYSTEMS (file system types to include) > > and we could add: > > $PRUNEFS (file system types to exclude) > > with the latter overriding $FILESYSTEMS ... > > As you may know, the new default for $FILESYSTEMS is all local, > non-synthetic, non-loopback, principally writable file system types > (which include msdosfs). The $PRUNEFS could be used to drop a few > that could be scanned, but where it is still not desirable. Sounds pretty flexible to me. While adding new config knobs is generally a thing to avoid, in this case they seem pretty orthogonal to each other. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071017125140.GA464>