Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57607 - [mlocate] updatedb.timer cannot be enabled

Attached to Project: Arch Linux
Opened by Vinay S Shastry (shastry) - Thursday, 22 February 2018, 14:24 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 22 February 2018, 15:52 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
updatedb.timer cannot be enabled as it's missing an Install section.

Needs this:

[Install]
WantedBy=timers.target


Additional info:
* mlocate 0.26-6

* systemctl output:
~ ❯❯❯ sudo systemctl enable updatedb.timer
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.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 22 February 2018, 15:52 GMT
Reason for closing:  Not a bug
Additional comments about closing:  It's statically enabled already

Loading...