Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!ulysses!hector!ekrell
From: ekrell@hector.UUCP (Eduardo Krell)
Newsgroups: comp.windows.x
Subject: Re: X11 & SHELL PROBLEM
Message-ID: <10216@ulysses.homer.nj.att.com>
Date: 8 Apr 88 18:00:57 GMT
References: <8804051303.AA03580@ATHENA.MIT.EDU>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: ekrell@hector (Eduardo Krell)
Organization: AT&T Bell Labs, Murray Hill
Lines: 24

In article <8804051303.AA03580@ATHENA.MIT.EDU> obrooks@NSWC-WO.ARPA.UUCP writes:
>
>	Upon termination of the server we return to the shell prompt
>if we use the C shell. But if we use the Bourne or Korn shell we get
>blown off the system and have to login again. I suspect that the 
>Korn or Bourne shells are not catching a signal;

No, the real problem is a bug in X Windows. xinit will put its stdout
and stderr in non-blocking mode (so that error messages from the X
server don't block). That's fine, but when you exit, it doesn't return
them to normal mode. When ksh or the Bourne Shell try to read from
their stdin, the read returns right away with an error status. Since
the shell can't read any more commands from its stdin, it dies.

The C shell was apparently fixed to handle this but the real fix doesn't
belong in the shell; it should be in X.

In the meantime, Dave Korn has fixed ksh and it now works fine.
If you don't have source for ksh, try running csh from ksh before
you run xinit. I remember that worked for me.
    
    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

    UUCP: {ihnp4,ucbvax}!ulysses!ekrell		ARPA: ekrell@ulysses.att.com