X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.3 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: <AANLkTinZTWvFyRG2nMZiyRm7=SizNi+LvP-jTZMeYfPe@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>
Date: Thu, 20 Jan 2011 16:28:17 +1300
Message-ID: <AANLkTimjEN_CoFZ3OJt2WCkFxMTjUG=7Pd3o=aSZsvS-@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
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Thu, Jan 20, 2011 at 13:06, David Antliff wrote:
> I haven't tried Cyrille's suggestion yet (but will)

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.

So it turned out to be something fairly simple in the end - but thank
you everyone for your advice.

Cyrille - I tried your script but it didn't seem to do anything. I had
a look over the source and I wasn't really able to work out what it
was doing. However it did give me the idea to copy/paste my entire
'env' from the working to non-working shell and then slowly eliminate
variables until I found the one I needed, so it was very helpful in an
indirect way - thank you.

Regards,

-- 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

