X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 17 Mar 2010 12:56:12 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: modification time of standard input is wrong Message-ID: <20100317115612.GH6505@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mar 16 18:24, Denis Excoffier wrote: > > Hello, > > Under Cygwin 1.7.1-1, i have created the small program (see below), > to print the modification time of the standard input. In the case where > the stdin is a pipe (or the terminal), i expect the result to be more > or less the current time. But the time printed in this case is > invariably the modification time of /dev/null. > > This has some impact in gzip and further, in tar. What impact? I don't think there is any standard which requires a non filesystem based stream to have a current timestamp and a tool relying on that might be broken. All our streams which are not backed by a filesystem w/ valid timestamps have an artificial timestamp of 2006-12-01 00:00:00. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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