X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: Invoking GUI programs over SSH Date: Wed, 19 Jan 2011 09:30:35 +0100 Lines: 23 Message-ID: References: <4D34B5F0 DOT 1060103 AT bopp DOT net> <4D34BD64 DOT 9050904 AT bopp DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/3.0.4 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com * David Antliff (Wed, 19 Jan 2011 11:59:39 +1300) > Jeremy: thank you also - ProcessMonitor is very useful, and I'm using > it to compare the behaviour of the working (local) and non-working > (over SSH) instances. It's going to take me some time to sift though > them, but there are big differences: > > Working: http://pastebin.com/W30xcT6P > Non-working: http://pastebin.com/Xt3an4Qs > > The two logs diverge massively at line 12. The working instance > appears to start scanning the filesystem, whereas the non-working > instance starts going through registry keys. I'm not 100% convinced > I'm comparing oranges with oranges here, but I'm hoping there's a clue > somewhere. > > I'll be spending some time trying to deduce what the problem might be, > but if anyone looks at those logs and can easily tell me, I'd really > appreciate it! :) I don't think anyone will do that unless you provide the logs in native (PML) format. Thorsten -- 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