slocate – Security Enhanced version of the GNU Locate
slocate [-qi] [-d] [–database= ]
slocate [-i] [-r ] [–regexp=]
slocate [-qv] [-o ] [–output=] slocate [-e] [-f ] <[-l ] [-c] <[-U ]
slocate [-Vh] [–version] [–help]DESCRIPTION
Secure Locate provides a secure way to index and quickly search for all files on your system regardless of ownership. It uses incremental
encoding just like GNU locate to compress its database to make searching faster, but it will also check file permissions and ownership
before displaying matched entries so that users will not see files they
do not have access to. Note that permissions and ownership are not
stored in the database.
This manual page documents slocate. slocate Enables system users to search entire filesystems without displaying unauthorized files.
-u Create slocate database starting at path /.
Create slocate database starting at path
Exclude directories from the slocate database.-f
Exclude files on specific file systems from the slocate
database.-c Parse /etc/updatedb.conf when updating the slocate database.
(see CONFIGURATION FILE below).
Security level. 0 turns security checks off. This will make
searchs faster. 1 turns security checks on. This is the
-i Does a case insensitive search.
-q Quiet mode. Error messages are suppressed.
Limit the amount of results shown to .
–regexp= Search the database using a basic POSIX regu
–output= Specfies the database to create.
–database= Specfies the path of databases to search in.-h –help Display this help.
-v –verbose Verbose mode. Display files when creating database.
-V –version Display version.
Colon-separated list of databases to search.
Secure Locate will parse GNU Locates /etc/updatedb.conf when the argu
ment is provided. But please be aware that Secure Locate currently does
NOT support all options provided by GNU Locates configuration file.
Options currently supported by Secure Locate are PRUNEFS and PRUNEPATHS
Secure Locate v3.0 beta
Kevin Lindsay – Copyright (c) 1999, 2000, 2001, 2002, 2003, 2004, 2005,
Report bugs to email@example.com
January 6, 2006 SLOCATE(1)