I think the problem is that the cron.daily plocate job isn't being run. I'd suspect the systemd timer doesn't work, but I'm not sure. I'll hack the cron.daily/plocate script to save some diagnostic information, and perhaps that'll help.
Thanks, .....Ron -- Ron Murray <r...@rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 On Sun, 2022-04-17 at 21:38 +0200, Steinar H. Gunderson wrote: > On Sat, Apr 09, 2022 at 07:50:09PM -0400, Ron Murray wrote: > > Steinar, you may be right about problems with the upgrade. I > > started > > looking into this earlier today because 'locate' couldn't find > > files > > that I knew were present in the filesystem. Based on what you said, > > I > > checked plocate.db and siscovered that it hadn't been updated since > > December 30. The files I was looking for had, of course, been added > > since then. > > That's strange; do you know if the updatedb.plocate command was ever > actually > run? Did it output anything to the error log? > > I've tried reproducing this by installing mlocate and then upgrading, > but I can't get it to break. > > > I also note that there's still a 'locate' in /etc/cron.daily, > > which > > runs '/usr/bin/updatedb.findutils'. Should these be still on the > > sysytem? Could they be interfering with plocate? > > No, it's entirely independent. > > /* Steinar */
