Your message dated Thu, 4 Jan 2024 15:02:42 +0100
with message-id <[email protected]>
and subject line Re: Bug#998389: mlocate systemd timer appears to force
execution at midnight, and the obvious override doesn't appear to be working
has caused the Debian Bug report #998389,
regarding mlocate systemd timer appears to force execution at midnight, and the
obvious override doesn't appear to be working
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
998389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998389
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mlocate
Version: 0.26-5
Severity: normal
The new systemd mlocate.timer causes all of my machines to run mlocate
exactly at midnight.
Neglecting that the stated rationale for the change to a 24hour splay
is a silly idea (the vast majority of people are neither running a
cluster, nor aren't at their computers between 2am and 6am), there is
no documentation to set otherwise (or return to the more sane system
default of being in cron.daily, which is already able to be splayed
according the admin's wishes).
Random advice on the internet was to chuck this in
/etc/systemd/system/mlocate.timer.d/override.conf and reload systemd,
but that resulted in no change to execution time:
[Timer]
AccuracySec=1h
OnCalendar=*-*-* 4:00
So what's the correct solution? Can that be documented?
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable'), (5, 'testing'), (2, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mlocate depends on:
ii adduser 3.118
ii libc6 2.31-13+deb11u2
mlocate recommends no packages.
Versions of packages mlocate suggests:
ii nocache 1.1-1+b1
-- Configuration Files:
/etc/updatedb.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Nov 03, 2021 at 03:08:45PM +0100, Steinar H. Gunderson wrote:
> FWIW, this is fixed in plocate, which replaces mlocate in bookworm.
> So this issue would potentially only be fixed in stable, and I doubt it would
> be relevant for a stable mlocate update.
mlocate in stable now is only a transition package, and it is entirely gone
from unstable, so closing this bug as obsolete.
/* Steinar */
--
Homepage: https://www.sesse.net/
--- End Message ---
