> Subject: Re: updatedb
>
> On 30/10/17 22:32, Patrick Dupre wrote:
> > Hello,
> >
> > updatedb does not run periodically.
> > Where should I initiate it (cron ?).
>
> I was wondering the same question earlier today when 'locate' failed to show a file
> I knew exists.
>
> I noticed that there is a related service:
>
> $ sudo systemctl status mlocate-updatedb
> [sudo] password for eyal:
> * mlocate-updatedb.service - Update a database for mlocate
> Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disabled
> Active: inactive (dead)
>
> I also see once daily ('round midnight) audit messages mentioning this service.
>
> Is it related? Should it be enabled?
I had the sale status.
Then I was able to run
systemctl start mlocate-updatedb
but
systemctl enable mlocate-updatedb
gives:
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
>
> [I run f26]
>
> > Thank.
> >
> > ===========================================================================
> > Patrick DUPRÉ | | email: pdupre@xxxxxxx
>
> --
> Eyal Lebedinsky (fedora@xxxxxxxxxxxxxx)
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
