Bug 74659

Summary:	up2date traceback on break
Product:	[Retired] Red Hat Linux	Reporter:	Gigs <jgiglio>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	gafton, mihai.ibanescu, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-08-06 22:46:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.