Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of burnlewis@gmail.com designates
 72.14.220.154 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=K6/oWqAI2vrjUyRG7UWBlI3oMCejezffGbPs29KU+fi4h/TaVAGIDPVHCEpEnF2H4b
         t/Uof/71J0sVqw/qcyAZEoly1atwDs7y45w9VPagxSqZX26jnAkJ+K0WZEOKpSrYF9cR
         pyh4GM/n1SP2R54rcIrbzbJhZdeLmCrQOsHUU=
MIME-Version: 1.0
In-Reply-To: <4A7AC3FC.2060004@gmail.com>
References: <4A78AFCA.9060607@gmail.com>
	 <12012a0a0908051143l234a0114w708bcadcd1fb91f5@mail.gmail.com>
	 <4A7AC3FC.2060004@gmail.com>
Date: Thu, 6 Aug 2009 09:45:26 -0400
Message-ID: <12012a0a0908060645r6eb52a9m7edcd46b94a0f33b@mail.gmail.com>
Subject: Re: UIMA AS java.io.IOException: Bad file descriptor when started in
	background on unix
From: Burn Lewis <burnlewis@gmail.com>
To: uima-user@incubator.apache.org
Content-Type: multipart/alternative; boundary=001485f19ac8060ec70470795578

--001485f19ac8060ec70470795578
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

We haven't been able to reproduce it ... probably depends on the version of
Linux (or the JVM) ... the way nohup deals with stdin appears to vary.
Another change was published yesterday (check if bytes available before
reading) but if that doesn't fix it for you we'll have to catch IOExceptions
from System.in ... since we can't test it would you mind adding a try/catch
and verifying?

- Burn.

--001485f19ac8060ec70470795578--