mcba@newt.phys.unsw.OZ.AU (Michael C. B. Ashley) (02/15/91)
Hi, I'm trying to setup a bunch of X-terminals hanging off a DEC5000 running ULTRIX 4.0, and have an interesting problem: if I run dxsession on more that one X-terminal under the same username, then when I quit dxsession on one terminal, I find that my window manager (dxwm) disappears on the other terminal (in addition to being logged out of the first terminal). I think my problem is that dxsession looks around for dxwm processes that are lying around, and kills any that appear to be attached to the same terminal. The trouble is that ULTRIX does not appear to know the terminal to which the dxwm processes are attached. For example, here is the output from ps -x PID TT STAT TIME COMMAND 11338 ? I 0:00 /usr/bin/dxwm 11987 ? I 0:00 /usr/bin/dxwm Here are two dxwm processes on two separate X-terminals. It is no wonder that dxsession doesn't know which one to kill. So, my question is: what do I have to do to make ULTRIX know the terminal to which a given dxwm is attached? I suspect that the problem is something to do with the /etc/ttys file. The entries I am using look like: :112 "/usr/bin/login -P /usr/local/ncd/Xprompter-ncd -C /usr/local/ncd/start-ncd" none on secure where the initial ":112" is used by the scripts Xprompter-ncd and start-ncd to work out the IP address of the X-terminal. ULTRIX knows that an entry of ":0" in /etc/ttys corresponds to "co" in a ps listing, and that "ttyp0" maps to "p0", but doesn't know what to do with ":112". I would be grateful for any help with this matter, thanks! Michael Ashley mcba@newt.phys.unsw.oz.au Astrophysics Dept. / Uni of NSW / Australia