DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=MW+vPVpNHBf8i4Rk
	HAR2qIvEjO3PY+av2jX7JIN1Re/7K1+SyJoyFxq4rCTwe1BBvxHNgT5f7ANGxNEF
	RgrgPUf8DWTrACgioyIwonej6lo6GrlTuaTTPoAGuRjE0ktkEszx2OslGQ3n5c+B
	lr6qcEN4Fl+qrzubYCzi3ZHivGk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: gawk: Bad File Descriptor error with concurrent readonly access to a network file
To: cygwin AT cygwin DOT com
References: <AB495CE313664A489959F8DEF45069A90188AA0710 AT EXSRV01 DOT avt-imst DOT local>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <56057D51.2010304@gmail.com>
Date: Fri, 25 Sep 2015 18:58:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <AB495CE313664A489959F8DEF45069A90188AA0710@EXSRV01.avt-imst.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 25/09/2015 18:31, Vermessung AVT - Wolfgang Rieger wrote:
> We let thousands of tiles undergo the same time consuming processing tasks. We use a multi core Windows 7 workstation running several tiles simultaneously in separate shell windows (parallel processing). A batch script controls the work flow of the task with gawk interpreting a number of setup / definition files at run time for each tile / working step. From time to time we get "Bad File Descriptor" errors in gawk (and, e.g., cat, head, tail) when accessing these setup files (they are only read). The full error line reads similar to:
>
> (With job.awk and first access to datafile.txt at gawk source line 31:)
>     "gawk: job.awk:31: fatal: error reading input file `datafile.txt': Bad file descriptor"
> (With inline gawk scripts typically:)
>     "gawk: fatal: error reading input file `datafile.txt': Bad file descriptor"
> (With something like "cat datafile.txt > destination":)
>     "cat: datafile.txt: Bad file descriptor"
>
> We use MS-Windows shell cmd.exe with batch scripts executing the gawk and other commands.
> I tried to use gawk's BEGINFILE rule in order to trap that error. However, the BEGINFILE block is never entered, rather, gawk immediately crashes with the "Bad File Descriptor" error.

Hi Wolfang,

"Bad file descriptor" just arose recently in another problem
https://cygwin.com/ml/cygwin/2015-09/msg00374.html
https://cygwin.com/ml/cygwin/2015-09/msg00436.html

Have you by chance some potential suspect like usual ones
   https://cygwin.com/faq/faq.html#faq.using.bloda

On your cygcheck output I notice nothing strange.

Can you provide the type of network disk with

/usr/lib/csih/getVolInfo <volumename>

Regards
Marco

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