Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <3.0.5.32.19990621200458.00958290@gis.net>
X-Sender: lhall AT gis DOT net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Mon, 21 Jun 1999 20:04:58 -0400
To: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
From: "Larry Hall (GIS)" <lhall AT rfk DOT com>
Subject: Re: File creation problem - cache?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

>Message-Id: <3 DOT 0 DOT 5 DOT 32 DOT 19990621085243 DOT 00a5c300 AT pop DOT ma DOT ultranet DOT com>
>X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
>X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
>Date: Mon, 21 Jun 1999 08:52:43 -0400
>To: Ian Collins <ianc AT kiwiplan DOT co DOT nz>,
>        "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
>Subject: Re: File creation problem - cache?
>In-Reply-To: <AC4D3D80B239D211BC140000F879A2BA0AEDA7 AT NTMAIL>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>
>At 04:19 PM 6/21/99 +1200, Ian Collins wrote:
>>Am I going mad, or does this sound familiar to anyone?
>>
>>We have a process that,
>>
>>1.1. Creates a file
>>1.2. Populates the file 
>>1.3. Closes the file
>>1.4, Forks a new process (with the filename created above as an argument).
>>
>>The child process,
>>
>>2.1. Looks for a file specified as an argument.
>>2.2. If found, reads and processes the file
>>
>>We are seeing, time and again, that the child does not find the specified
>>filename.
>>However, by putting a delay between 1.4 and 2.1, the problem disappears.
>>
>>Is there a caching problem?
>>Can anyone suggest a reliable work around?
>>
>>(Or am I just going mad).
>>
>>Ian Collins.
>>
>>
>>
>
>
>Are you on 9x?  I remember seeing this problem on 9x without Cygwin.
>The problem basically equated to the fact that the file was not available 
>in the directory until it showed up in the explorer (or at least that
>was the easy way to describe when it would and when it would not work).
>Similar troubles on NT (using NTFS at least) did not appear.  My solution
>at the time was similar to yours (i.e. wait "awhile" and things show up).
>Its not an optimal solution by any means but it can work.  Others may
>have found better solutions...
>
>
>Larry Hall                              lhall AT rfk DOT com
>RFK Partners, Inc.                      http://www.rfk.com
>118 Washington Street                   (508) 893-9779 - RFK Office
>Holliston, MA 01746                     (508) 893-9889 - FAX
>                                        (508) 560-1285 - cell phone
>

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com