On Tue, 2009-05-19 at 12:59 +0200, Piotr Engelking wrote: > On i386 system with amd64 kernel, iotop exits without printing anything: > > $ iotop -b || echo $? > 1 > $ > > Running without -b additionally corrupts the terminal. > > The problem is that ioprio.find_ioprio_get_syscall_number() uses uname -m to > find syscall numbers, which breaks on biarch systems. On i386/amd64 in > particular, iotop calls exit_group(2) instead of ioprio_get(2) as a result. > > Please use something like dpkg-architecture instead of uname. Better yet, > use a less fragile method of dispatching syscalls, if you can think of sane > one.
Guillaume, any idea about how to fix this one? dpkg-architecture is obviously the wrong solution since it isn't cross-distro. I guess the right way to fix this would be to create a C-based syscall python module that would embed some syscall numbers from #include <sys/syscall.h>? -- bye, pabs http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
