You are not logged in.
Hello everyone!
It seems like my laptop is making a lot of requests to openpgpkey.archlinux.org, about every 5-10 seconds. Does anyone know why this is the case? Or how to lower the interval?
Thanks in advance
Offline
I guess this is caused by "archlinux-keyring-wkd-sync.service" and the related timer that take care of syncing the keyring from the web directory
Offline
how to lower the interval?
# systemctl mask archlinux-keyring-wkd-sync
Note that just disabling the service or timer doesn't stop it because the Arch developers have decided to treat the users as if they were small children
Last edited by Head_on_a_Stick (2024-09-05 14:05:42)
"Austerity is the idea that the global financial crash of 2008 was caused by there being too many libraries in Wolverhampton."
— Alexei Sayle
Offline
The service should not run every 5-10 seconds unless it fails, so check the services status or your system journal itr.
systemctl status archlinux-keyring-wkd-sync.service
@HoaS, why would/does disabling the timer not work?
https://wiki.archlinux.org/title/System … Management
Offline
why would/does disabling the timer not work?
It will get re-enabled after the archlinux-keyring package is updated:
https://gitlab.archlinux.org/archlinux/ … =heads#L74
Not cool, Arch devs, not cool.
"Austerity is the idea that the global financial crash of 2008 was caused by there being too many libraries in Wolverhampton."
— Alexei Sayle
Offline
@Head_on_a_Stick proficient users can just NoExtract the files, others are better off like this But this is not related to the original question, so lets keep it at this ..
Offline
proficient users can just NoExtract the files, others are better off like this
Well this "non-proficient" user is extremely irritated that they have to do that at all. Forcefully enabling services goes against the basic ethos of Arch. IMO.
EDIT: and anyway using NoExtract wouldn't stop you sneaky bastards enabling the service through some other underhand, devious method
Last edited by Head_on_a_Stick (2024-09-05 15:42:38)
"Austerity is the idea that the global financial crash of 2008 was caused by there being too many libraries in Wolverhampton."
— Alexei Sayle
Offline
The timer could be activated via post-install (not post-update) hook, but ftr. there're several "mandatory" timers (man-db, updatedb, shadow, logrotate, tmpfiles-clean, …) that are just installed with some package, so it's not specifically aggressive.
Offline
there're several "mandatory" timers (man-db, updatedb, shadow, logrotate, tmpfiles-clean, …) that are just installed with some package
But those are supplied by upstream.
it's not specifically aggressive
Of course not. Apologies to all if that's how I came across.
"Austerity is the idea that the global financial crash of 2008 was caused by there being too many libraries in Wolverhampton."
— Alexei Sayle
Offline
So is the keyring timer, it's just, like w/ pacman, a more incestuous relationship between up- and downstream.
Offline
The service should not run every 5-10 seconds unless it fails, so check the services status or your system journal itr.
Wel.....
○ archlinux-keyring-wkd-sync.service - Refresh existing keys of archlinux-keyring
Loaded: loaded (/usr/lib/systemd/system/archlinux-keyring-wkd-sync.service; static)
Active: inactive (dead)
TriggeredBy: ● archlinux-keyring-wkd-sync.timer
FYI: I didn't change a single thing except reboot since last time.
Although now it doesn't seem to be spamming requests anymore?
Offline
Presumingly it succeeded, or the timer has given up until next week - did it actually reach the server or are you aware of the traffic because you were intercepting it?
What happens if you just start it?
systemctl start archlinux-keyring-wkd-sync.service
Offline