On Sun, 27 Apr 2025 13:32:45 -0400 Haines Brown <hai...@histomat.net> wrote:
> I know locate can be slow, but I waited a sufficient time. I suspect > locate has to build a database, but my system has been running a week. If things are working correctly, and you installed plocate rather than locate, you should see something like: root@testing:/media/installer# journalctl -b | grep -i updatedb Apr 24 23:44:17 testing systemd[1]: Started plocate-updatedb.timer - Update the plocate database daily. Apr 25 03:35:39 testing systemd[1]: Starting plocate-updatedb.service - Update the plocate database... Apr 25 03:35:40 testing systemd[1]: plocate-updatedb.service: Deactivated successfully. Apr 25 03:35:40 testing systemd[1]: Finished plocate-updatedb.service - Update the plocate database. Apr 25 03:35:40 testing systemd[1]: plocate-updatedb.service: Consumed 526ms CPU time, 168.7M memory peak. Apr 26 03:48:39 testing systemd[1]: Starting plocate-updatedb.service - Update the plocate database... Apr 26 03:48:39 testing systemd[1]: plocate-updatedb.service: Deactivated successfully. Apr 26 03:48:39 testing systemd[1]: Finished plocate-updatedb.service - Update the plocate database. Apr 26 03:48:39 testing systemd[1]: plocate-updatedb.service: Consumed 361ms CPU time, 153.1M memory peak. Apr 27 03:23:39 testing systemd[1]: Starting plocate-updatedb.service - Update the plocate database... Apr 27 03:23:39 testing systemd[1]: plocate-updatedb.service: Deactivated successfully. Apr 27 03:23:39 testing systemd[1]: Finished plocate-updatedb.service - Update the plocate database. Apr 27 03:23:39 testing systemd[1]: plocate-updatedb.service: Consumed 434ms CPU time, 153.2M memory peak. root@testing:/media/installer# -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
