earle@POSEUR.JPL.NASA.GOV (Greg Earle - Sun JPL on-site Software Support) (10/23/89)
This seems peculiar: When my Sun-3/160 is running X (with `awm' running), if I go to an NCD16 X terminal, use the telnet window to log onto my Sun, and run my `startx-ncd' script (which is basically a replicant of my .xinitrc file, except that it sets DISPLAY to the NCD, and doesn't `exec' the final xterm), all of the clients come up just fine - but both `awm' and `twm' complain that they think I am running another window manager (`uwm' seems to work). Even giving them an explicit `-display ncd:0.0' doesn't help. Both `awm' and `twm' will complain if they try to set the properties of the root window (SubstructureRedirectMask, KeyPressMask & friends) and it fails. Since the clients all come up OK, I figured that the `dpy' returned by XOpenDisplay would be universally correctly set to the NCD's server, and thus any operations on the root window would correctly reference the NCD. But it sorta seems like perhaps `awm' and `twm' are really noticing that my own Sun server is running a window manager that has changed the properties instead, and thus they complain. Since I am running two different displays from the same machine, I assumed that therefore I needed a separate window manager invocation for each one. Is there any likely explanation for the above behaviour, and if so how can I correct it? - Greg Earle earle@poseur.JPL.NASA.GOV Disclaimer: I have enough problems with my employer as it is without you deciding that I am somehow speaking for them, so don't even think about it. These are my own opinions only!