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:
hmm, yes. Tracebacks bad. Will take a look at adding support for catching stdout going away.
fixed a while ago. rh8/9 versions and later should handle this gracefully.