Le 27/09/2024 à 16:05, Jonathan Kamens a écrit :
Just to be clear, the script is not "hanging" or "locking itself in a
loop," it is throttling its performance so interactive performance for
the user isn't impacted by the work apt-listchanges is doing in the
background.
Having said that, you're 100% correct that the number of CPUs is a
better load average limit than 1. I will make that change in the next
release. Thank you for the suggestion!
Yeah, sorry, maybe my wording wasn't accurate (English is not my native
language). I didn't meant to say that the script was hanging, but it
seemed so when run through the systemd service, since it didn't write
any output (except when it couldn't retrieve local packages' changelogs).
It's only when I ran the script directly with --debug that I understood
what was going on.
Thanks for considering my suggestion :)
Regards,
--
Raphaël Halimi
