Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 13 Apr 2005 13:34:29 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: regression in utime Message-ID: <20050413173429.GA5792@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <041320051446 DOT 13106 DOT 425D30B900003E300000333222069984990A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <041320051446.13106.425D30B900003E300000333222069984990A050E040D0C079D0A@comcast.net> User-Agent: Mutt/1.5.8i On Wed, Apr 13, 2005 at 02:46:17PM +0000, Eric Blake wrote: >I'm not sure when this regressed, but in comparing logs of coreutils >testsuite runs, sometime between 1.5.12 and 1.5.14 utime() was broken >with regards to fifos. It is still broken in the 20050412 snapshot: > >$ mkfifo foo >$ touch foo >touch: setting times of `foo': Invalid argument > >It used to return successfully (I'm not sure whether it actually >touched times in 1.5.12, only that it didn't die with EINVAL). This should successfully touch foo in the latest snapshot. cgf -- 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/