Bug 2934 - Problem with stdout output to console with RH6.0
Problem with stdout output to console with RH6.0
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
Depends On:
  Show dependency treegraph
Reported: 1999-05-20 08:10 EDT by urs.rohrer
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-09-23 12:29:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description urs.rohrer 1999-05-20 08:10:52 EDT
- Before sending this message I have checked the FAQs and
the DejaNews forums to see if there are any questions and
solutions concerning my problem. No indications found.

Here my problem:

- If I start a program written in Tcl/Tk+csh+Fortran with
xterm -e program, then no stdout output is showing up in the
xterm window as it was the case with previous versions of
Redhat Linux.
- Similar things happen when I start up some of my programs
in /etc/rc.d/rc5.d. The printf output does not show up
anymore in the console/xconsole as with previous versions of
Redhat Linux. (The call for the xconsole I found removed
from the /etc/X11/xdm/Xsetup_0 file.)

- I am running kde as my primary desktop, but gnome may also
be choosen. I start up with a customized 2.2.5-15 kernel and
I am using Accelerated-X as well as the OSS sound card

Many thanks for your considerations.
      Urs Rohrer
Comment 1 Preston Brown 1999-07-06 10:25:59 EDT
we need more information.  Can you show us a simple (5-10 line)
example program which will exercise this problem?  Is the problem
locale specific? Any other details are appreciated.
Comment 2 Preston Brown 1999-09-23 12:29:59 EDT
closed due to lack of feedback.  If you are still having a problem
please reopen the bug.

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