Re: can't start remote X programs

From: Darren Tucker (dtucker_at_gate.dodgy.net.au)
Date: 06/04/05

  • Next message: maccozet: "vente neuf modem box neuve" 
    Date: 04 Jun 2005 14:32:57 GMT

    On 2005-06-04, Tomasz Chmielewski <tch@nospam.unc.edu> wrote:
    > I have two computers running Linux and openssh-4.1p1.
    >
    > They are connect to each other through an OpenVPN tunnel.
    >
    > If I connect from BROKEN to GOOD using ssh -X ..., I can start remote X
    > programs without problems (for example, xclock).
    >
    > When I connect from GOOD to BROKEN, I can't start remote X programs:

    Worth a try:
    http://www.openssh.com/faq.html#3.13

    but my money is on this:
    http://www.snailbook.com/faq/mtu-mismatch.auto.html

    (Richard: perhaps add "PPPoE" and "VPN" as common contributors to this?)

    [...]
    > And I can wait forever, but xclock is not started on my local machine.
    > I can't kill it with ctrl+C.
    >
    > When I do "ps x" on BROKEN, it shows xclock is running.
    > When I kill it (killall xclock), I can't use the terminal on which I
    > started anymore.

    I'll bet if you do a "netstat" on both ends and find you ssh connection
    you'll see a constant or increasing number int he "Send-Q" at the ssh
    server end. 

    -- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
  • Next message: maccozet: "vente neuf modem box neuve"

    Relevant Pages

    • Re: kill xterm kills app!
      ... When you kill the xterm or gnome-terminal all the processes with it ... If you do "xclock &" you do nothing special to manage the HUP signal. ... > thing that 'nohup' does when starting it as mentioned in earlier posts. ... > $ disown xclock ...
      (Fedora)
    • cant start remote X programs
      ... I have two computers running Linux and openssh-4.1p1. ... xclock). ... debug1: channel 1: new [x11] ... When I kill it, I can't use the terminal on which I ...
      (comp.security.ssh)