home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!sgiblab!nec-gw!nec-tyo!wnoc-tyo-news!scslwide!wsgw!wsservra!onoe
- From: rns@deakin.OZ.AU (Robert Sturrock)
- Newsgroups: fj.mail-lists.x-window
- Subject: Re: setting DISPLAY env variable
- Message-ID: <1992Dec21.145609.26329@sm.sony.co.jp>
- Date: 21 Dec 92 14:56:09 GMT
- Sender: onoe@sm.sony.co.jp (Atsushi Onoe)
- Distribution: fj
- Organization: Deakin University
- Lines: 21
- Approved: michael@sm.sony.co.jp
-
- Date: 21 Dec 92 12:02:42 GMT
- Message-Id: <1h4bp2INNi8u@sol.deakin.OZ.AU>
- Newsgroups: comp.windows.x
- References: <1gmgnoINN4bu@sol.deakin.OZ.AU>, <BzCzvA.42s@constellation.ecn.uoknor.edu>
- Sender: xpert-request@expo.lcs.mit.edu
-
- dwight@geohub.gcn.uoknor.edu (Dwight D. Moore) writes:
-
- >Try using "xterm -display wkstn:0" instead of depending on the
- >DISPLAY environment variable. There are scripts around that
- >will do an rsh and allow you to do the above command without
- >explicitly logging into the machine. We have setup window
- >manager menus with pulldowns to do just this and popup
- >a remote window.
-
- I don't think this solves the problem. My difficulty is not starting
- up an xterm. My problem is logging into a remote machine and having the
- DISPLAY variable appropriately set on this machine to "wkstn:0.0".
-
-
- Rob
-