X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 10 Mar 2008 17:11:15 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Problem with Cygwin and ClearCase Message-ID: <20080310211115.GA14583@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20080310201053 DOT GA17124 AT panix DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080310201053.GA17124@panix.com> User-Agent: Mutt/1.5.16 (2007-06-09) 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 Mon, Mar 10, 2008 at 04:10:53PM -0400, David Arnstein wrote: >I just upgraded ClearCase to a new version and immediately I have >new problems relating to Cygwin. >[snip] >I am writing to this mail list to inquire what is "special" about >processes started by a Cygwin bash process. "Special," when compared to >launching from a DOS box or from a standard Windows shortcut. Thanks >for any suggestions. We prefer the term "gifted" to "special". But, seriously, there is no simple answer to your question. Cygwin obviously manages to start all manner of normal Windows programs. It uses the standard Windows API to accomplish this so there is no way to know why ClearCase would not be reacting well without quite a bit of code investigation and, possibly, without help from ClearCase themselves. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/