The point is that I am not sure that mlocate (or updatedb) runs properly because locate does not find my new files ! How can I be sure that mlocate runs properly ? Thank. =========================================================================== Patrick DUPRÉ | | email: pdupre@xxxxxxx Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France =========================================================================== > Sent: Monday, September 19, 2016 at 9:15 PM > From: "Tom Horsley" <horsley1953@xxxxxxxxx> > To: "Patrick Dupre" <pdupre@xxxxxxx> > Cc: users@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: anacron/cron > > On Mon, 19 Sep 2016 20:47:20 +0200 > Patrick Dupre wrote: > > > Sorry, but I do not have > > /etc/cron.daily/mlocate.cron > > This is all part of the systemd fungus experience as it > attempts to engulph all of linux. > > An rpm -q --list mlocate shows these files on my fedora 24 > system: > > /usr/lib/systemd/system/mlocate-updatedb.service > /usr/lib/systemd/system/mlocate-updatedb.timer > > So it is now running on a systemd timer, not in cron > (this helps make sure no one has any idea what the heck > is going on). > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
