X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Reply-To:	sebastian AT smashd DOT net
Date:	Wed, 25 Jul 2012 17:43:52 -0500
Message-ID:	<CANhU=OgrNxMpHStRVjG+Pf_kQtZDECw6Oa7yL7vXnu63-Y9F9Q@mail.gmail.com>
Subject:	environment variables & mks toolkit - patch opportunity?
From:	"M. Sebastian Comella" <sebastian AT smashd DOT net>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Hi all -
I recently lost a good chunk of my day tracking down a Cygwin issue
ultimately caused by an installation of IBM InfoSphere. The InfoSphere
installer surreptitiously installed MKS Toolkit, which in turn set a
bunch of environment variables that left Cygwin in a very unhelpful
state: attempting to start Cygwin via its usual mintty shortcut would
appear to hang, with mintty showing "sh.exe" in its title bar and
little else. The cause of the issue is unfortunately not very obvious
since there is no error message or other form of reporting. If I had
realized that MKS Toolkit was being installed I might have had a
fighting chance, but without that info I was in the dark.

Fortunately, fixing the issue is pretty easy and is a matter of
removing some Windows environment variables, as noted in this
2002-vintage thread:

http://www.cygwin.com/ml/cygwin/2002-07/msg00734.html

My question is this: is there an opportunity to patch something in
Cygwin's startup "chain" to detect unsavory environment variables and
warn users in some fashion? I'm not sure what package (or core
process) could detect the situation and still get a warning off to the
user before everything goes fubar. Putting a check into the installer
may also be a viable solution, considering that the first thing I did
was run the Cygwin installer again to see if it could "repair" things.

I think I can take care of writing the patch, but I'd like some input
on where it even belongs before I give it a shot.


Thanks!

Sebastian.

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

- Raw text -