updatedb 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.
updatedb is usually run daily by cron(8) to update the default database.
updatedb returns with exit status 0 on success, 1 on error.
The PRUNE_BIND_MOUNTS, PRUNEFS, PRUNENAMES and PRUNEPATHS variables, which are modified by some of the options, are documented in detail in updatedb.conf(5).
locate(1) outputs entries as absolute path names which don't contain symbolic links, regardless of the form of PATH.
If 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.
If FLAG 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 "others".
To create a private mlocate database as an user other than root, run
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.
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.
Miloslav Trmac <firstname.lastname@example.org>
locate(1), mlocate.db(5), updatedb.conf(5)