public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel Colascione <dan.colascione@gmail.com>
To: cygwin@cygwin.com
Cc: Alberto Canestrelli <canestrelli@idra.unipd.it>
Subject: Re: X-forwarding very very slow
Date: Wed, 18 Aug 2010 15:50:00 -0000	[thread overview]
Message-ID: <4C6C0129.1050309@gmail.com> (raw)
In-Reply-To: <4C6BFF90.6030404@idra.unipd.it>

On 8/18/10 8:43 AM, Alberto Canestrelli wrote:
> I have a problem with Cygwin. I am connecting from USA by ssh to the
> Hector supermachine in Edinburgh ( I write "startx" in Cygwin and then I
> use  "ssh -Y  v1acanes@login.hector.ac.uk" ). Everything works fine, the
> only problem is that the forwarding of the windows is very very slow. It
> takes sometimes also up to 5 minutes to open a new window. I am
> debugging a code with Totalview and it is a impossible to work. I am in
> contact with the Hector support and with their computer they tried to
> run Cygwin under windows and connecting by ssh (exactly like I am doing)
> and they say that x-forwarding  is fast.

The performance they're seeing probably has little to do with their
Cygwin version --- they're a lot closer, after all, so support's latency
is probably a lot lower.

NX actually works under Cygwin, though it's a pain to compile (and
unsupported I imagine). This document provides an introduction to
getting the system to work:

http://www.nomachine.com/documentation/building-components.php


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2010-08-18 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 15:43 Alberto Canestrelli
2010-08-18 15:50 ` Daniel Colascione [this message]
2010-08-18 16:01   ` Larry Hall (Cygwin)
2010-08-18 16:55 ` Csaba Raduly
2010-08-18 21:35   ` Jeremy Bopp
2010-08-24 12:21     ` Ryan Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C6C0129.1050309@gmail.com \
    --to=dan.colascione@gmail.com \
    --cc=canestrelli@idra.unipd.it \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).