From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs64023ebc; Thu, 28 Jan 2010 12:24:37 -0800 (PST) Received: by 10.91.19.27 with SMTP id w27mr164234agi.118.1264710275439; Thu, 28 Jan 2010 12:24:35 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 28si3316080gxk.2.2010.01.28.12.24.34; Thu, 28 Jan 2010 12:24:35 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B48D51858313; Thu, 28 Jan 2010 15:24:34 -0500 (EST) Received: from mail-iw0-f193.google.com (mail-iw0-f193.google.com [209.85.223.193]) by rubyforge.org (Postfix) with ESMTP id 11EF41858306 for ; Thu, 28 Jan 2010 15:21:57 -0500 (EST) Received: by iwn33 with SMTP id 33so1077816iwn.0 for ; Thu, 28 Jan 2010 12:21:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:subject:from:to :in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=kzrRTMQ7U3sfgVyYo2whEdrYkH2UGIsZRfEHj7TS5vU=; b=WcOWUXi5WpkOVXVrofymAkEhQNjWTrWY/D9RFC4sn+ueuSfej5l16JjishAJd2KqYB nExDWjmqu8ba+gd0BGsqGoMBJ2yy8QsxxVeZCWCRWbGIlEqYX1f8j02Fxrrw9xAWZfVq WEOfHa4LOrfWN3O2huvaL+n/EUrbysMxNRJRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; b=GgYOYmypOX13+MxbR0S+RgKvcpKHjAYVy+TlFZTOqK8JOpAAD7mDK86ZObIMapYJjE vQPG2VXwL6gh/PuoWyseq7/4+89N5MkZnl4uiW24YjZRCavVJYI526PRfKfvUJrnHmPy 6LwWKHOaZu5NwFnXLIzG8a8cqGdrOLs4V343U= Received: by 10.231.145.196 with SMTP id e4mr3252271ibv.54.1264710117439; Thu, 28 Jan 2010 12:21:57 -0800 (PST) Received: from localhost (c-76-98-110-216.hsd1.nj.comcast.net [76.98.110.216]) by mx.google.com with ESMTPS id 23sm1232493iwn.3.2010.01.28.12.21.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Jan 2010 12:21:56 -0800 (PST) From: Eric Sherman To: sup-devel In-reply-to: <1264709164.82.0.12859120302.issue57@masanjin.net> References: <1264709164.82.0.12859120302.issue57@masanjin.net> Date: Thu, 28 Jan 2010 15:21:54 -0500 Message-Id: <1264709474-sup-4387@changeling.local> User-Agent: Sup/git Subject: Re: [sup-devel] [issue57] Request: Flush changes periodically X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from Anirudh Sanjeev's message of Thu Jan 28 15:06:04 -0500 2010: > > Can there be an optional functionality to flush changes to disk every 10-15 > minutes, instead of having to press $ every time You may want to try these patches: [PATCHv3] idle and unidle updates [1] [PATCH] flush index on idle [2] The first one relays the idle and unidle updates, and the second one will actually perform the flush when it gets an idle update. And you may be interested in this one too: [PATCHv5] [issue14] poll updates accumulate while idle [3] I use these and they meet my needs. [1]: http://rubyforge.org/pipermail/sup-devel/2010-January/000285.html [2]: http://rubyforge.org/pipermail/sup-devel/2010-January/000274.html [3]: http://rubyforge.org/pipermail/sup-devel/2010-January/000241.html _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel