update a database for mlocate
see also :
add an example, a script, a trick and tips
To create a private mlocate database as an user other than
updatedb -l 0 -o db_file -U
Note that all users that can read db_file can get the
complete list of files in the subtree of source_directory.
creates or updates a database used by locate(1). If
the database already exists, its data is reused to avoid
rereading directories that have not changed.
is usually run daily by cron(8) to update the default
PRUNE_BIND_MOUNTS, PRUNEFS, PRUNENAMES
and PRUNEPATHS variables, which are modified by some
of the options, are documented in detail in
-f, --add-prunefs FS
Add entries in
white-space-separated list FS to PRUNEFS.
Add entries in
white-space-separated list NAMES to
Add entries in
white-space-separated list PATHS to
Store only results of scanning
the file system subtree rooted at PATH to the
generated database. The whole file system is scanned by
outputs entries as absolute path names which don’t
contain symbolic links, regardless of the form of
Write debugging information
about pruning decisions to standard error output.
Write a summary of the
available options to standard output and exit
Write the database to
FILE instead of using the default database.
Set PRUNE_BIND_MOUNTS to
FLAG, overriding the configuration file.
Set PRUNEFS to
FS, overriding the configuration file.
Set PRUNENAMES to
NAMES, overriding the configuration file.
Set PRUNEPATHS to
PATHS, overriding the configuration file.
Set the “require file
visibility before reporting it” flag in the generated
database to FLAG.
is 0 or no, or if the database file is
readable by "others" or it is not owned by
mlocate, locate(1) outputs the database
entries even if the user running locate(1) could not
have read the directory necessary to find out the file
described by the database entry.
is 1 or yes (the default), locate(1)
checks the permissions of parent directories of each entry
before reporting it to the invoking user. To make the file
existence truly hidden from other users, the database group
is set to mlocate and the database permissions
prohibit reading the database by users using other means
than locate(1), which is set-gid mlocate.
Note that the
visibility flag is checked only if the database is owned by
mlocate and it is not readable by
Output path names of files to
standard output, as soon as they are found.
Write information about the
version and license of locate on standard output and
updatedb returns with exit status 0 on success, 1 on
A configuration file. See updatedb.conf(5).
The database updated by default.
The accompanying locate(1) utility was designed to be
compatible to slocate and attempts to be compatible to
GNU locate where possible. This is not the
case for updatedb.
Databases built with --require-visibility no allow users
to find names of files and directories of other users, which they
would not otherwise be able to do.