On 8/2/21 10:52 AM, Dave Ulrick wrote:
Any thoughts? Have I discovered a bug with mlocate-updatedb.timer or
mlocate-updatedb.service?
Just now I disabled mlocate-updatedb.timer and added an entry to root's
crontab (using 'crontab -e'):
SHELL=/bin/sh
PATH=/usr/local/bin:/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
...
minute hour * * * /usr/libexec/mlocate-run-updatedb
I set hour to the current hour and minute to one minute in the future,
then I waited for the time to occur, checked to see if
/var/lib/mlocate/mlocate.db showed a new timestamp, and ran 'locate
bin/myth'. Files under /usr/bin were included. Compare with the
mlocate-updatedb.timer method: files under /usr/bin are omitted.
To work around this issue, I've disabled mlocate-updatedb.timer and will
use crontab instead.
Dave
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
