X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <4D34BD64 DOT 9050904 AT bopp DOT net> <20110119155957 DOT GA12142 AT ednor DOT casa DOT cgf DOT cx> Date: Thu, 20 Jan 2011 18:31:25 +1300 Message-ID: Subject: Re: Invoking GUI programs over SSH From: David Antliff To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 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. But for a bash shell running over ssh, this option is not set, so coupled with git's strange autocrlf behaviour in Cygwin (which I have reported before) this leads to bash scripts that are freshly cloned from git being un-runnable from an ssh session. So my question is - how do I get the bash shell that runs when I ssh to a Cygwin host to have the SHELLOPTS=igncr option set? Somehow I need to get the sshd service to spawn the new bash instance with this option set. 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. -- David. -- 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