Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!WORK8.ICASE.EDU!tom
From: tom@WORK8.ICASE.EDU (Tom Crockett)
Newsgroups: comp.windows.x
Subject: Re: R3 xterm and controlling tty's and awm
Message-ID: <8812091324.AA02733@work8.icase.edu>
Date: 9 Dec 88 13:24:58 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 33


>  I can confirm this behaviour if you run your awm from the xterm console
>  window.  Typically we don't do this rather we run awm from xinit and then
>  use the awm -e option to startup my initial set of clients.  


I have been using awm from the R3 tape + patch08, and have found it impossible
to do the following:

  xinit awm -e $HOME/.xinitrc

Awm -e always seems to crash in this situation.  Has anyone else seen this
behavior?  Any thoughts on what might be causing it?  We are running R3 +
fixes1-2 + Purdue-speedups under SunOS 3.5 on Sun 3/50s.

We also have another annoying problem:  window manager restarts (f.restart)
invoked from a menu often cause the server to terminate.  This is not
consistent.  It seems to happen roughly once out of every three restarts.
Could this be because awm is somehow causing the clients to die?  I have to
admit I haven't spent a whole lot of effort looking into the causes -- I have
more pressing things to work on.  I can't recall seeing this problem in R2, or
least not with anything approaching this frequency.



Tom Crockett

--------------------------------------------------------------------------------
Institute for Computer Applications in Science and Engineering
M.S. 132C, NASA Langley Research Center
Hampton, VA  23665

e-mail:  tom@icase.edu		phone:   (804) 865-4097
--------------------------------------------------------------------------------