Just a heads up, folks. On
and
No, you likely reinstalled
mlocate
mlocate and plocate are either installed to, or available in the repositories of, all of the 90 or so Linux distros I run.
However the
command at terminal, used is simply
...
Not trying to throw shade, but I only installed
mlocate after locate failed to generate the file:
*************************************
priestapostate@XXXXXX:~$ apt search locate | grep locate/stable
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
dlocate/stable 1.12 all
locate/stable,now 4.9.0-4 amd64 [installed]
mlocate/stable,now 1.1.18-1 all [installed]
node-p-locate/stable 6.0.0-12 all
plocate/stable,now 1.1.18-1 amd64 [installed,automatic]
They show up as two separate packages when I perform an apt search:
*************************************
locate/stable,now 4.9.0-4 amd64 [installed]
maintain and query an index of a directory tree
*************************************
*************************************
priestapostate@XXXXXX:~$ apt search mlocate
Sorting... Done
Full Text Search... Done
mlocate/stable,now 1.1.18-1 all [installed]
transitional dummy package
plocate/stable,now 1.1.18-1 amd64 [installed,automatic]
much faster locate
*************************************
My point is (once again: not trying to be snarky, or throw shade) that I did manually install locate.
Arch Wiki have this, in part
If you have to install mlocate or plocate on your distro, and wish to use it in the same session, you must first run
before the command commencing
locate
will have success
Other than that, if you introduce new packages to your system run updatedb again in session.
In other circumstances, when you reboot your computer.
updatedb
will run automatically to update the database.
I can't answer to that.
Yes it was, or should have been.
Both mlocate and plocate are in the Package List for your Debian 12 'Bookworm'.
The easiest way to locate updatedb.conf is to run
Mine in this LM 21.3 'Virginia' Cinnamon shows this
Code:
chris@VirginiaCinn-WD:~$ locate updatedb.conf
/etc/updatedb.conf
/usr/share/man/man5/updatedb.conf.5.gz
... and that location is the same for my Debian 12 'Bookworm' Cinnamon.
Okay, this is where I have another point of confusion.
I didn't perform the locate command on the updatedb.conf, as I wouldn't have thought to do that for a few reasons:
1. If --
as mentioned in my studies, the locate command required the updatedb.conf file (that the system didn't detect) -- in order to properly run the updatedb command (which was failing to run), then wouldn't that have failed? I mean, I wouldn't have thought to place the updatedb.conf file in the /usr/share/man directory - so I would think that the system would have placed it there, and known to look for the file there - which it didn't.
2. If the locate command seemed to be malformed/corrupted/misconfigured in such a way as to not have the necessary updatedb.conf file, wouldn't it make sense to not use it as a tool?