Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 24 Aug 2005 00:43:43 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Please try a snapshot - complete request
Message-ID: <20050824044343.GB17539@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20050822181856 DOT GA6914 AT trixie DOT casa DOT cgf DOT cx> <20050824014431 DOT GA17967 AT trixie DOT casa DOT cgf DOT cx> <20050824014953 DOT GA18130 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050824014953.GA18130@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.8i

On Wed, Aug 24, 2005 at 01:19:27AM +0000, Eric Blake wrote:
>Snapshot 20050823 19:00:09 is hanging on Win98 (I've been noticing this for a
>week or more of previous snapshots, now, but don't know when the bug was
>introduced).  Oftentimes I get a Windows popup claiming that cat has performed
>an illegal operation, at which point the system is low on memory and can't spawn
>any more processes, so I am forced to reboot.  This idiom is part of the
>coreutils configure script.
>
>$ cat /proc/uptime
>284.85 0.00
>$ cat < /proc/uptime
># no response after 10 minutes, Ctrl-C and Ctrl-D do nothing                                                                        
Huh.  This seemed to be silently dying on XP, too.  It was not so
forgiving on Me, though, as you noted.

This should be fixed in the 20050824 snapshot and "cat < /proc/uptime"
do the right thing now, i.e., print the uptime.

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/