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: Fri, 22 Nov 2002 19:34:04 +0900 From: Anthony Heading To: cygwin AT cygwin DOT com Subject: Any known issues with signal delivery on 2-cpu boxes? Message-ID: <20021122103404.GA7875@tkd-fires-02.ja.jpmorgan.com> References: <20021122044722 DOT GA8875 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021122044722.GA8875@redhat.com> User-Agent: Mutt/1.4i On Thu, Nov 21, 2002 at 11:47:22PM -0500, Christopher Faylor wrote: > I'm regenerating a snapshot right now which may become 1.3.16. > Please try it. Might I ask whether there are any fixes or remaining known problems with signals being lost on multi-processor machines? The much reported 'rsync hangs' bug (search for those words in the mail-archive if interested) I hunted down last month to SIGUSR2 being issued by one half of an rsync fork but not received by the other. The bug is apparently still there - frustratingly intermittent, I can't now reproduce it myself with the latest cygwin release, but a colleague of mine is seeing it about 50% of the time. However we've only ever hit the problem on dual processor boxes. I'm happy to keep exploring, but there have been no responses by any of the cygwin experts to the bug reports, so I'm not clear whether cygwin is simply not expected to handle signals reliably on a dual processor box, or whether simply not enough information has been given. Thanks Anthony This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. -- 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/