Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Problem with cat under bash shell
Date:	Thu, 16 Sep 2004 18:10:46 +0100
MIME-Version:	1.0
In-Reply-To:	<20040916170058.GE17670@cygbert.vinschen.de>
Message-ID:	<NUTMEGi66G0qMFYRESA0000002a@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	16 Sep 2004 17:10:47.0046 (UTC) FILETIME=[1BA58A60:01C49C10]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Corinna Vinschen
> Sent: 16 September 2004 18:01

> On Sep 16 17:48, Dave Korn wrote:

> >   Ah, but you probably don't use it in such a 3PP-kind of 
> way as having your
> > /tmp on a remotely-mounted network share.....
> 
> Funny you say that.  In my case the server is running Linux 2.4.27 and
> Samba 2.2.8...  But the description in the KB article is *that* close
> to what we observe here.

  If it's really a simple matter of the file getting deleted too early, you
could verify it fairly simply by waiting for a keypress in between the
CloseHandle call and the subsequent ReadFile call, and then just go and
manually do a "ls /tmp" in another window to see if the file had vanished
already or not.




    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -