After reading through CONFIG_TASK_DELAY_ACCT error in "iotop" kernel 5.14 , I found that the python version of iotop
has the issue resolved via CONFIG_TASK_DELAY_ACCT error in “iotop” kernel 5.14 · Issue #21 · Tomas-M/iotop · GitHub .
I’m assuming of course that the fix doesn’t end up also require the same https://superuser.com/questions/610581/iotop-complains-config-task-delay-acct-not-enabled-in-kernel-only-for-specific “workaround” of adding GRUB_CMDLINE_LINUX_DEFAULT="delayacct"
to /etc/default/grub
I’ve missed using iotop
since moving to the 5.14 kernel and look forward to the update hitting our repositories.
What update?
The latest version is Iotop 0.6 (NEWS )
I think you mean iotop-c
which is in the AUR and is currently up to date with the release version. Feel free to create an iotop-c-git
VCS package if you want the latest commits.
1 Like
and here I thought I was being careful not to confuse iotop
and iotop-c
… and ended up confusing them anyway.
I’ll hold tight to see if the python version gets a similar update down the road… if not, I’ll replace it with the AUR iotop-c
.
Thank you @Yochanan
EDIT: Oh, I see what happened. Public Git Hosting - iotop.git/commit and Public Git Hosting - iotop.git/commit “links to the fix” were really references to the fixed iotop-c
, not fixes to the python version.
system
Closed
22 November 2021 17:32
4
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.