Bug 74659 - up2date traceback on break
Summary: up2date traceback on break
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 7.3
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-30 01:07 UTC by Gigs
Modified: 2015-01-08 00:00 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-08-06 22:46:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Gigs 2002-09-30 01:07:25 UTC
Description of Problem:
up2date will traceback rather than showing the proper error message if it 
loses its stdout, e.g. when piping output to "more" and hit ctrl-C

Version-Release number of selected component (if applicable):
up2date-2.7.86-7.x.3

How Reproducible:
Always, but seemingly variable error messages

Steps to Reproduce:
1. up2date --showall | more
2. ctrl-C after output begins
3. 

Actual Results:
[root@xxxxx root]# Traceback (innermost last):
  File "/usr/sbin/up2date", line 1171, in ?
    print "\nAborted."
IOError: [Errno 32] Broken pipe

or

Traceback (innermost last):
  File "/usr/sbin/up2date", line 1177, in ?
    print _("There was some sort of I/O error: %s") % e
IOError: [Errno 32] Broken pipe

Expected Results:


Additional Information:

Comment 1 Adrian Likins 2002-10-01 21:59:31 UTC
hmm, yes. Tracebacks bad. 

Will take a look at adding support for catching stdout going away.

Comment 2 Adrian Likins 2003-08-06 22:46:50 UTC
fixed a while ago. rh8/9 versions and later should handle this
gracefully. 


Note You need to log in before you can comment on or make changes to this bug.