Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ub!planck!meyer From: meyer@planck.uucp (Bob Meyer) Newsgroups: comp.windows.x Subject: Re: Setting display name for X windows server Message-ID: <1990Sep14.033455.11976@planck.uucp> Date: 14 Sep 90 03:34:55 GMT References: <1990Sep12.220114.11571@d.cs.okstate.edu> Organization: Calspan Advanced Technology Center Lines: 41 In article <1990Sep12.220114.11571@d.cs.okstate.edu> minich@d.cs.okstate.edu (MINICH ROBERT JOHN) writes: >Please reply via e-mail to minich@d.cs.okstate.edu > > Someone please relieve some frustrtation and help me get an IBM RT running X >windows to let another machine throw up a window or two. The RT like to put >"unix:0" in the DISPLAY enviornment variable but nothing on the local can find >that. (Not too suprising!) Now, I can't find where/how to tell the RT to use >something like the machine name for DISPLAY. Ideally, it would be >"f.cs.okstate.edu:0" but I can't find any clue in the x manuals from IBM as to >how to do this. (Nor in the Sequent manuals, but I don't think they have x >capability on their console...) The way that I fixed this is to put lines like: XDISPLAY=$HOST:0 export XDISPLAY into my '.xinitrc' file before it provokes 'mwm'. I then put the argument: '-display $XDISPLAY' into every window manager command that tries to run a remote application. The alternative is to use the 'rcmd' shell script that was posted some time ago. It seems to realize that 'unix:0' won't cut it for a remote application. 'rcmd' also performs the 'rsh' in such a way as not to generate a 'stopped: tty output' message. I haven't even considered trying to run 'mwm' on an X-terminal because of this problem. Imagine a situation where you fire up mwm on the Xterminal, then start provoking process after process trying to figure out why they won't run, much to the dismay of the poor guy sitting at the machine's console :-). BTW, 'rcmd' also takes care of the 'xhost ' for you if you are running from the console display (or actually, any server that is running on the machine as opposed to an X-terminal where the server is actually executing in the terminal). -- Thinking quickly, the IBM System Jock # Bob Meyer uttered an incantation in EBCDIC and made # Calspan Advanced Tech. Center the sign of the Terminated Fork. # meyer%planck.uucp@acsu.buffalo.edu The UNIX Guru only smiled and trapped him in a recursive SED script.