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
