X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.4 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: Robert Miles <robertmiles@bellsouth.net>
cc: cygwin@cygwin.com
Subject: Re: YA call for snapshot testing
In-reply-to: <4F20D59D.6030204@bellsouth.net>
References: <20120122054719.GB28773@ednor.casa.cgf.cx> <20120122055300.GB657@ednor.casa.cgf.cx> <4F1BBB0F.2020009@gmail.com> <20120122165705.GA10996@ednor.casa.cgf.cx> <4F1C5F56.8070208@gmail.com> <20120122193306.GA12886@ednor.casa.cgf.cx> <4F1C759D.9010704@shaddybaddah.name> <29235.1327446059@freon.franz.com> <4F1F422E.9040507@cygwin.com> <13884.1327471385@freon.franz.com> <20120125062835.GD18425@ednor.casa.cgf.cx> <22712.1327521524@freon.franz.com> <4F20D59D.6030204@bellsouth.net>
Comments: In-reply-to Robert Miles <robertmiles@bellsouth.net>   message dated "Wed, 25 Jan 2012 22:25:01 -0600."
Date: Wed, 25 Jan 2012 20:51:54 -0800
Message-ID: <7424.1327553514@freon.franz.com>
From: Kevin Layer <layer@franz.com>
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

Robert Miles wrote:

>> > NOTE: I run with CYGWIN="nodosfilewarning proc_retry:1" because I run
>> > a lot of non-cygwin software from shell scripts, and during testing,
>> > that can take 10's of minutes, I can't afford to have those programs
>> > restarted if they crash on exit.  Before setting proc_retry:1, I once
>> > saw a loop of a 30 minute test run that went on for 10+ iterations.
>> >
>> Are you able to put that CYGWIN setting inside the shell scripts that
>> need it, and therefore not have it apply to any other scripts?

For remotely executed stuff (an rsh-like program that allows execution
of commands on a windows host), I use the trick of setting it on the
command line.   (It's unlike rsh in that it returns exit codes, and it
pre-dates sshd for windows.)

For stuff executed on the windows machine, we use a system env var
that has it set.


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