LinuxReviws.org --get your your Linux knowledge
> Linux Reviews > Manual Pages (man) >

updatedb

update the slocate database


  1. updatedb.1.man
  2. updatedb.8.man


1. updatedb.1.man

Manpage of UPDATEDB

UPDATEDB

Section: User Commands (1)
Index Return to Main Contents
 

NAME

updatedb - update the slocate database  

SYNOPSIS

updatedb [-u] [-U path] [-e path1,path2,...] [-f fstype1,...] [-l [01] ] [-q] [-v,--verbose] [-V, --version] [-h, --help] pattern...  

DESCRIPTION

This manual page documents slocate, a security-enhanced version of locate. updatedb is simply a link to slocate that implies the -u option.  

OPTIONS

-u
Create slocate database starting at the root directory. This is the default behavior when called as updatedb.
-U path
Create slocate database starting at path path.
-e dirs
Exclude directories in the comma-separated list dirs from the slocate database.
-f fstypes
Exclude file systems in the comma-separated list dirs from the slocate database.
-l <num>
Security level. -l 0 turns security checks off, which will make searches faster. -l 1 turns security checks on. This is the default.
-q
Quiet mode; error messages are suppressed.
-v
Verbose mode; display files indexed when creating database
--help
Print a summary of the options to slocate and exit.
--version
Print the version number of slocate and exit.
 

CONFIGURATION FILE

Secure Locate's updatedb will automatically parse GNU Locate's /etc/updatedb.conf. But please be aware that Secure Locate currently does NOT support all options provided by GNU Locate's configuration file.

Options currently supported by Secure Locate are PRUNEFS and PRUNEPATHS  

SEE ALSO

slocate(1)


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
CONFIGURATION FILE
SEE ALSO

This document was created by man2html using the manual pages.
Time: 17:32:55 GMT, October 23, 2013

2. updatedb.8.man

Manpage of updatedb

updatedb

Section: Maintenance Commands (8)
Updated: Jun 2008
Index Return to Main Contents

 

NAME

updatedb - update a database for mlocate

 

SYNOPSIS

updatedb [OPTION]...

 

DESCRIPTION

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.

 

EXIT STATUS

updatedb returns with exit status 0 on success, 1 on error.

 

OPTIONS

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).

-f, --add-prunefs FS
Add entries in white-space-separated list FS to PRUNEFS.

-n, --add-prunenames NAMES
Add entries in white-space-separated list NAMES to PRUNENAMES.

-e, --add-prunepaths PATHS
Add entries in white-space-separated list PATHS to PRUNEPATHS.

-U, --database-root PATH
Store only results of scanning the file system subtree rooted at PATH to the generated database. The whole file system is scanned by default.

locate(1) outputs entries as absolute path names which don't contain symbolic links, regardless of the form of PATH.

--debug-pruning
Write debugging information about pruning decisions to standard error output.

-h, --help
Write a summary of the available options to standard output and exit successfully.

-o, --output FILE
Write the database to FILE instead of using the default database.

--prune-bind-mounts FLAG
Set PRUNE_BIND_MOUNTS to FLAG, overriding the configuration file.

--prunefs FS
Set PRUNEFS to FS, overriding the configuration file.

--prunenames NAMES
Set PRUNENAMES to NAMES, overriding the configuration file.

--prunepaths PATHS
Set PRUNEPATHS to PATHS, overriding the configuration file.

-l, --require-visibility FLAG
Set the ``require file visibility before reporting it'' flag in the generated database to FLAG.

If FLAG is 0 or no, or if the database file is readable by "others" or it is not owned by locate, 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 locate and the database permissions prohibit reading the database by users using other means than locate(1), which is set-gid locate.

Note that the visibility flag is checked only if the database is owned by locate and it is not readable by "others".

-v, --verbose
Output path names of files to standard output, as soon as they are found.

-V, --version
Write information about the version and license of locate on standard output and exit successfully.

 

EXAMPLES

To create a private mlocate database as an user other than root, run
updatedb -l 0 -o db_file -U source_directory
Note that all users that can read db_file can get the complete list of files in the subtree of source_directory.

 

FILES

/etc/updatedb.conf
A configuration file. See updatedb.conf(5).

/var/lib/mlocate/mlocate.db
The database updated by default.

 

SECURITY

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.

 

NOTES

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.

 

AUTHOR

Miloslav Trmac <mitr@redhat.com>

 

SEE ALSO

locate(1), mlocate.db(5), updatedb.conf(5)


 

Index

NAME
SYNOPSIS
DESCRIPTION
EXIT STATUS
OPTIONS
EXAMPLES
FILES
SECURITY
NOTES
AUTHOR
SEE ALSO

This document was created by man2html using the manual pages.
Time: 17:32:55 GMT, October 23, 2013

ENGLISH - ja - pl

Meet new people