Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!emory!mephisto!eedsp!fourier!eric
From: eric@fourier.eedsp.gatech.edu (Eric Hyche)
Newsgroups: comp.windows.x
Subject: Can someone help a dying xterm?
Keywords: xterm,help
Message-ID: <1076@eedsp.eedsp.gatech.edu>
Date: 13 Aug 90 19:54:44 GMT
Sender: news@eedsp.eedsp.gatech.edu
Reply-To: eric@fourier.eedsp.gatech.edu (Eric Hyche)
Distribution: usa
Organization: Georgia Institute of Technology
Lines: 34


Eric Hyche
Georgia Tech, School of Electrical Engineering, Atlanta, GA  30332
USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!gt-eedsp!eric
INTERNET: eric@medinfo.gatech.edu

I am running X11 R3 on a Sun 3/260 running SunOS 4.0.1. Today, I noticed
that the xterms
I start up in my ".x11start" file don't know about any of the
environment variables they
need to. So I went into .x11start and added a "-ls" to the lines which
start up the
xterms. Shortly thereafter, after I had exited X, I returned to X by
typing "startx" (
our startup script) and after the two xterms had gotten started, X
suddenly ended, with the
message:

xterm: Broken pipe

Not only did it end, but it insufferably tied up the console keyboard.
Every time a key was
pressed, LOTS of characters came up on the screen. Ctrl-C and Ctrl-Z did
not work, and
alas, I had to put it out of its misery with a fastboot. Does anybody
know what's going on
here? Our local X guru is out of town.

Note: I do not know for sure that the "-ls" caused the problem. I
changed my ".x11start" file
back to what it was before, and then attempted to restart X. No dice.
Same problem.

Thanks!