Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1338986

Summary: Output of tcsh builtin command "jobs" now goes to stderror.
Product: Red Hat Enterprise Linux 6 Reporter: Paulo Andrade <pandrade>
Component: tcshAssignee: David Kaspar // Dee'Kej <deekej>
Status: CLOSED ERRATA QA Contact: Iveta Wiedermann <isenfeld>
Severity: medium Docs Contact: Lenka Špačková <lkuprova>
Priority: urgent    
Version: 6.8CC: bnater, fkrska, karlamrhein, mkolaja
Target Milestone: rcKeywords: Patch, Regression, Reproducer, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: tcsh-6.17-36.el6 Doc Type: Release Note
Doc Text:
Output of "jobs" in *tcsh* is now correctly displayed to stdout Previously, the output of the "jobs" built-in command was displayed to standard error instead of standard output. This bug has been fixed, and the output of "jobs" is now correctly displayed to stdout.
Story Points: ---
Clone Of:
: 1338987 1357127 (view as bug list) Environment:
Last Closed: 2017-03-21 11:18:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1357127    

Description Paulo Andrade 2016-05-23 20:22:48 UTC
Simple reproducer:

---8<---
$ sleep 60 &
[1] 17210
$ jobs -l
[1]  + 17210 Running                       sleep 60
]$ jobs -l > out
[1]  + 17210 Running                       sleep 60
$ cat out
$
$  jobs -l >& err
$ cat err
[1]  + 17210 Running                       sleep 60
---8<---

This is a regression in rhel-6.8, and rhel-7.3, caused by
the patch to correct #1019321 (tcsh prints error message
on standard output instead of stderr).

Comment 2 David Kaspar // Dee'Kej 2016-05-24 11:52:20 UTC
Yes, this is definitely a regression. I will be contacting upstream about this during today.

Comment 3 David Kaspar // Dee'Kej 2016-05-24 12:37:59 UTC
Upstream has been informed:
http://mx.gw.com/pipermail/tcsh-bugs/2016-May/001048.html

Comment 4 David Kaspar // Dee'Kej 2016-05-26 13:22:43 UTC
Here are the commits that should fix the regression (from upstream):
https://github.com/tcsh-org/tcsh/commit/17d484bfacf46f
https://github.com/tcsh-org/tcsh/commit/50029cb5d4fe43

Comment 11 David Kaspar // Dee'Kej 2016-10-21 09:36:06 UTC
I have closed this by mistake (thought this was fixed in RHEL 6.7.z), reopening...

Comment 15 errata-xmlrpc 2017-03-21 11:18:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0731.html