dixons%phvax.dnet@SMITHKLINE.COM (09/17/90)
Tony Facca (fsfacca@avelon.lerc.nasa.gov) writes: >I have a question about the xhost program. Actually, what I am trying to do >is use toolchest to open xterm clients on remote machines. Under 3.2 >this worked just fine. I do an "xhost remote_host" and follow that up >with "rsh remote_host xterm -display local_host:0" [basically] > >Anyway, I now have 3.3 running on several of the systems and this method no >longer works. I think its a problem with xhost as evidenced by the following: [etc] I have noticed a similar problem with gettin xhost to pay attention to commands. It seems to respond OK but then forgets what you tell it. It occured to me that maybe I needed to have the X server up and running before using xhost so I started up xclock and then tried xhost. That solved the problem for me. I don't think that this is the behaviour under 3.2 but seems to happen under 3.3. Also, I haven't gone back to see if the xhost changes are remembered after you log out or not. See if that works for you. Scott Dixon (dixons@smithkline.com)
mikey@eukanuba.wpd.sgi.com (Mike Yang) (09/18/90)
In article <9009170230.AA00690@smithkline.com>, dixons%phvax.dnet@SMITHKLINE.COM writes: |> I have noticed a similar problem with gettin xhost to pay attention to |> commands. It seems to respond OK but then forgets what you tell it. The X server will reset itself when there are no clients. Therefore, if your server is running but you have no X clients, when you run xhost it establishes a connection, it does its stuff, it exits, the X server resets and effectively undoes what xhost did. The solution, as you noticed, is to run an X client to keep the server from resetting when xhost exits, ----------------------------------------------------------------------- Mike Yang Silicon Graphics, Inc. mikey@sgi.com 415/335-1786