MIME-Version: 1.0
In-Reply-To: <AANLkTi=MCUP3s5mYPR=imTv7oCD=R3dZJiV0GJFQ7ub8@mail.gmail.com>
References: <AANLkTi=m0aJ+xo6Gcr_CYWtMcVJjc0SBxfubnuXeg3Br@mail.gmail.com>	<4D34BD64.9050904@bopp.net>	<AANLkTi=9rNRhtx=dwQari9v+Rrsun9Yg1VwgTnZoNeLz@mail.gmail.com>	<AANLkTikujecFG_j4-E1z8tD_9Zupy1TpW_cdFeJ52XTW@mail.gmail.com>	<ih3ntk$7aj$1@dough.gmane.org>	<AANLkTik5jFdKfG8Gza89zECW92Tu6tdV+xKUk_9=0SgH@mail.gmail.com>	<ih67fc$fnq$1@dough.gmane.org>	<AANLkTik0rxN_Y5AAfoJEs-+KTt87f6MA+f7P_m0KpQBD@mail.gmail.com>	<ih6lo8$ita$3@dough.gmane.org>	<AANLkTikz150UHB_VLvirv2cc4MX8NcwVM2ZiPQ8r7uFk@mail.gmail.com>	<20110119155957.GA12142@ednor.casa.cgf.cx>	<AANLkTimgcSSawumtUp9tAHXxf77zGHstsz5bmu9muOyQ@mail.gmail.com>	<AANLkTinZTWvFyRG2nMZiyRm7=SizNi+LvP-jTZMeYfPe@mail.gmail.com>	<AANLkTimjEN_CoFZ3OJt2WCkFxMTjUG=7Pd3o=aSZsvS-@mail.gmail.com>	<AANLkTi=MCUP3s5mYPR=imTv7oCD=R3dZJiV0GJFQ7ub8@mail.gmail.com>
Date: Thu, 20 Jan 2011 18:31:25 +1300
Message-ID: <AANLkTinHwssWvKax7R-mkPvgMN6v6Ma6D5r--YT9kuhe@mail.gmail.com>
Subject: Re: Invoking GUI programs over SSH
From: David Antliff <david.antliff@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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