X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KAM_THEBAT,KHOP_THREADED,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Date: Sat, 19 Jan 2013 00:18:39 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <1213214325.20130119001839@mtu-net.ru> To: Corinna Vinschen Subject: Re: rtorrent and recent snapshots - apparent problem with msync() In-Reply-To: <20130118160742.GH11791@calimero.vinschen.de> References: <20130117062415.GB24529@ednor.casa.cgf.cx> <20130118003522.GA1913@ednor.casa.cgf.cx> <20130118093205.GB11791@calimero.vinschen.de> <20130118154352.GA23471@ednor.casa.cgf.cx> <20130118160742.GH11791@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 Greetings, Corinna Vinschen! >> I saw that you made another change to this function. Is it possible that >> this might actually fix the "rtorrent problem"? > No. It only adds the MS_SYNC handling. rtorrent uses MS_ASYNC. That made me think... If rtorrent uses MS_ASYNC, shouldn't *rtorrent* be prepared for consequences? Instead of you trying to satisfy its expectations? > I think there's basically no way around the loop. I'm just still > wondering if we shouldn't add a cygwait() call to handle signals > during the wait time. -- WBR, Andrey Repin (anrdaemon@freemail.ru) 19.01.2013, <00:15> Sorry for my terrible english... -- 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