X-Recipient: archive-cygwin@delorie.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@cygwin.com From: Thorsten Kampe Subject: Re: Invoking GUI programs over SSH Date: Thu, 20 Jan 2011 08:06:18 +0100 Lines: 23 Message-ID: References: <4D34BD64.9050904@bopp.net> <20110119155957.GA12142@ednor.casa.cgf.cx> 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@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com * David Antliff (Thu, 20 Jan 2011 18:31:25 +1300) > On Thu, Jan 20, 2011 at 16:28, David Antliff wrote: > > Ok, an update - I've managed to solve this problem - the vendor > > informed me (indirectly) that the error I was seeing was due to the > > access of files in c:\lsc_env - turns out I hadn't ensured that the > > LSC_INI_PATH environment variable was set properly in the 'ssh' > > instance. > > Actually there is one outstanding issue with this "Hudson slaves over > SSH" issue - due to the inability for Cygwin's bash to run scripts > with DOS line endings, we've had to use SHELLOPTS=igncr in our > Cygwin.bat files, since it cannot be modified once bash is running. Convert the shell scripts to LF endings. > I did a search and found an old cygwin mailing list thread > from 2007 that resulted in "use the new version of Cygwin", which I > believe I have covered as I'm using Cygwin 1.7.5. Sorry, but this seems to get a bit ridiculous: http://cygwin.com/ -> "Current Cygwin DLL version"... Thorten -- 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