From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs62689ebc; Thu, 28 Jan 2010 12:06:19 -0800 (PST) Received: by 10.90.188.5 with SMTP id l5mr199614agf.73.1264709177737; Thu, 28 Jan 2010 12:06:17 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 19si2256032gxk.68.2010.01.28.12.06.17; Thu, 28 Jan 2010 12:06:17 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 0ECDD185830C; Thu, 28 Jan 2010 15:06:16 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 3D5DE18582EE for ; Thu, 28 Jan 2010 15:06:07 -0500 (EST) Received: from localhost ([127.0.0.1] helo=entry.masanjin.net) by entry.masanjin.net with esmtp (Exim 4.69) (envelope-from ) id 1Naacu-0004eA-VI for sup-devel@rubyforge.org; Thu, 28 Jan 2010 15:06:06 -0500 MIME-Version: 1.0 To: sup-devel@rubyforge.org From: Anirudh Sanjeev Date: Thu, 28 Jan 2010 20:06:04 +0000 Precedence: bulk X-Roundup-Name: Sup issue tracker X-Roundup-Loop: hello X-Roundup-Version: 1.4.10 Message-Id: <1264709164.82.0.12859120302.issue57@masanjin.net> X-Roundup-issue-status: unread X-Roundup-issue-priority: feature request In-Reply-To: <1264709164.82.0.12859120302.issue57@masanjin.net> Subject: [sup-devel] [issue57] Request: Flush changes periodically X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Reply-To: Sup issue tracker , Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org New submission from Anirudh Sanjeev : Can there be an optional functionality to flush changes to disk every 10-15 minutes, instead of having to press $ every time Rationale: I'm in a place where power cuts are extremely frequent. I keep forgetting to flush changes manually requiring me to re-delete and archive my messages every time I reboot and restart sup. I run sup off of git 'next' head. A patch which will hard-code this functionality would be fine as well. Alternatively, is there a command I can call via a cron job to do this? Thanks! ---------- messages: 142 nosy: anirudhs priority: feature request ruby_version: 1.8 status: unread sup_version: git/next title: Request: Flush changes periodically _________________________________________ Sup issue tracker _________________________________________ _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel