Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Fri, 13 Jul 2001 23:37:09 +0200
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: File timestamp not updated by writes with current snapshot?
Message-ID: <20010713233709.L25442@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4 DOT 3 DOT 1 DOT 2 DOT 20010713162617 DOT 016af9d0 AT pop DOT ma DOT ultranet DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20010713162617 DOT 016af9d0 AT pop DOT ma DOT ultranet DOT com> <20010713203843 DOT 11034 DOT qmail AT lizard DOT curl DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20010713165236 DOT 0240fb80 AT pop DOT ma DOT ultranet DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <4.3.1.2.20010713165236.0240fb80@pop.ma.ultranet.com>; from lhall@rfk.com on Fri, Jul 13, 2001 at 05:26:42PM -0400

On Fri, Jul 13, 2001 at 05:26:42PM -0400, Larry Hall (RFK Partners, Inc) wrote:
> At 04:38 PM 7/13/2001, Jonathan Kamens wrote:
> > >  Date: Fri, 13 Jul 2001 16:33:12 -0400
> > >  From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
> > >  
> > >  Windows has trouble with times/date resolution.  In that respect, this is 
> > >  known.  What DLL did you update from?  I see it with 1.3.2 and 1.1.8.
> >
> >I updated from the current head, which I guess is 1.3.2+.
> >
> >Now that you mention it, I just tried the test with 1.1.8, and you're
> >right, the particular test case I mentioned happens there too.
> >
> >But what prompted me to send E-mail about this problem to the mailing
> >list isn't a test case which spans only one minute.  It was seeing a
> >file being regularly updated with new data (coming from a >> bash
> >redirection) for *over forty minutes* without its timestamp being
> >updated.  I could be wrong, but I don't think I've ever seen that with
> >1.1.8.
> >
> >Or perhaps I'm just on drugs and this problem has been around for a
> >long long time :-).
> 
> 
> I'm not sure exactly how long the problem may have existed either.  It
> is a problem with the form, rather than the function.  Splitting this
> up into separate statements all run from a script doesn't show the 
> problem.  Have you tried the same thing on other platforms?  I'm just
> curious if the problem is Cygwin specific or not.  I'm not near a 
> functioning Linux box at the moment... :-(

No, it doesn't happen on Linux.

The problem is related to the fact that the whole command set is
running in a subshell while the stdout redirection is already done
by the parent shell. I don't know why that happens, though.
Just a wild guess: The file has been opened by another process than
the process writing to the file and that opening process has the
file opened all the time. Perhaps Windows has a timestamp problem
related to that situation somehow. At least Cygwin doesn't explicitely
care for the timestamps on simple IO but relies on the underlying OS.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/