ktl@wag.caltech.edu (Kian-Tat Lim) (05/09/91)
I just brought up xdm from the MIT sources running on OpenWindows. Aside from the fact that I can't get the server to properly reset after a session to allow the login window to be put up again (have to restart it), I have a major problem with cmdtools and shelltools (XView version). First, keeping the default openwin-* files led to cmdtools that chewed up CPU time while their corresponding shells sat in T state. Perusal of xdm-errors showed that they were having TIOCSPGRP problems. OK -- I seem to remember a net posting from a while back mentioning that setsid(8V) was necessary. I prefixed this to every cmdtool command in .openwin-init (run from .xsession) and openwin-menu. Now what happens is that the "terminals", though functional, have a very strange initial state. I've been getting bad entries for rows, columns, intr, erase, etc. in 'stty -a' output. 'stty sane' fixes things up, but it seems to me that this shouldn't be necessary. What am I messing up here? -- Kian-Tat Lim (ktl@wag.caltech.edu, KTL @ CITCHEM.BITNET, GEnie: K.LIM1)