X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/XBc3VsXgNEBGCb34R/nay Date: Fri, 18 Jan 2013 16:24:13 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: rtorrent and recent snapshots - apparent problem with msync() Message-ID: <20130118212413.GA9011@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20130117062415 DOT GB24529 AT ednor DOT casa DOT cgf DOT cx> <20130118003522 DOT GA1913 AT ednor DOT casa DOT cgf DOT cx> <20130118093205 DOT GB11791 AT calimero DOT vinschen DOT de> <20130118154352 DOT GA23471 AT ednor DOT casa DOT cgf DOT cx> <20130118160742 DOT GH11791 AT calimero DOT vinschen DOT de> <1213214325 DOT 20130119001839 AT mtu-net DOT ru> <20130118211025 DOT GB519 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130118211025.GB519@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Fri, Jan 18, 2013 at 04:10:25PM -0500, Christopher Faylor wrote: >On Sat, Jan 19, 2013 at 12:18:39AM +0400, Andrey Repin wrote: >>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? > >It does seem that way. Actually, it isn't that clear. It seems like msync is failing in the MS_ASYNC case when it shouldn't be, i.e., rtorrent is within its rights to expect the operation to succeed. -- 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