On 28.06.2023 18:06, Kilian Hanich wrote:
Well, in this case we have a major problem because a lot of users will likely never notice.
This problem is years old, even before systemd started to use github issue tracker. So far nobody came up with a solution (at least, with an actual implementation of such solution).
Although we could deal with this (and possible future accidents) via systemd.preset and calling systemctl preset $UNIT in the scriplets.
Which is no solution because it ignores decision of local administrator.
Am 28.06.23 um 16:49 schrieb Thorsten Kukuk:
On Wed, Jun 28, Kilian Hanich wrote:
IMPORTANT: please check that the wtmpdb-update-boot.service and wtmpdb-rotate.timer are enabled, if not, please enable them: systemctl enable --now wtmpdb-update-boot.service systemctl enable wtmpdb-rotate.timer
I would guess most users aren't subscribed to this mailing list and as such won't do this because they don't know about it.
So, is this being dealt with in a future update?
Until now nobody has an idea how to "fix" this with an update: it's no longer possible to distinguished between "not enabled because of the bug" and "not enabled because admin did disable it".
Thorsten
-- Sincerely
Kilian Hanich