Arch Linux

Salkay

Member

Registered: 2014-05-22

Posts: 644

[SOLVED] plocate systemd timer

mlocate has recently been replaced by plocate. This seems to be a drop-in replacement, and appears to work fine if I manually updatedb or locate. However, I'm a bit confused as to how to use the systemd timer.

My understanding is that we should both enable and start the timer. Apparently (like normal services) enable the timer will make it work on next boot, and start will make it work now. start seems to work fine (according to systemctl list-timers --all), but enable seems to fail.

$ sudo systemctl enable plocate-updatedb.timer
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

Is there something I'm doing wrong, or is there something wrong with the systemd timer?

Last edited by Salkay (2024-09-11 06:21:19)

seth

Member

Registered: 2012-09-03

Posts: 59,324

Re: [SOLVED] plocate systemd timer

https://gitlab.archlinux.org/archlinux/ … type=heads which matches the previous mlocate updatedb.timer

systemctl status plocate-updatedb.timer

Should be active, the timer cannot be disabled.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Salkay

Member

Registered: 2014-05-22

Posts: 644

Re: [SOLVED] plocate systemd timer

Ah okay, that makes sense. Thanks again @seth.