locate cannot find a file you created a few minutes ago. Type the command, run as root, that rebuilds the database locate searches.

LPIC-1 Exam 101-500, objective 104. Devices, Linux filesystems, filesystem hierarchy standard easy

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

Answer

Type the answer.

Accepted answer

Case sensitive — Linux is, and grading LS as ls would teach a falsehood.

Why

locate is fast because it never touches the filesystem at search time: it queries a database, normally under /var/lib/mlocate/ or /var/lib/plocate/, that updatedb builds by walking the tree. Distributions run updatedb from a daily cron job or systemd timer, so anything newer than the last run is invisible until you run it yourself. Its behaviour, including which paths and filesystem types to skip, is configured in /etc/updatedb.conf. find, by contrast, always searches live.

Where this comes from

Cited
LPI exam objective 104.7
What it says
Locate files with locate and maintain its database with updatedb.

Practise this

Reading one question is not practice. The trainer will draw a short set from objective 104 and space the ones you get wrong.

Practise LPIC-1 Exam 101-500

More questions on this objective

All questions on Devices, Linux filesystems, filesystem hierarchy standard

Practise LPIC-1 Exam 101-500