iotop -bo output can't be piped

Bug #337882 reported by Keith Worrell
2
Affects Status Importance Assigned to Milestone
iotop (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: iotop

Attempting to pipe 'iotop -bo' or 'optop -bo 2>&1' to anything produced no output until after hitting 'ctrl-c' at which point produced the following:
---
^Cclose failed in file object destructor:
Error in sys.excepthook:

Original exception was:
---

iotop -b had no problems as far as I could tell

The easiest and most revealing way of producing this error was with 'iotop -bo | cat', but same error with sed and tee.

Using iotop version 0.2-3 (jaunty) and Ubuntu 9.04

I had expected it to work like 'top -bi | foo'

Related branches

Revision history for this message
Paul Wise (Debian) (pabs) wrote :

This bug is fixed upstream:

http://repo.or.cz/w/iotop.git?a=commit;h=5be2a70fcffefacf1a5695bd0d2d2edc51ffa2f1

It will be fixed once upstream has made a new release and I've packaged it for Debian.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iotop - 0.3-1

---------------
iotop (0.3-1) unstable; urgency=low

  * New upstream release
    - displays IO scheduling class and priority (Closes: #521360)
    - iotop -bo output can now be piped (LP: #337882)
    - 01_fix_nfs_crash.patch was included, drop it
  * Bump Standards-Version, no changes needed

 -- Ubuntu Archive Auto-Sync <email address hidden> Tue, 05 May 2009 09:14:31 +0100

Changed in iotop (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.