From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.182.92.230 with SMTP id cp6csp577401obb; Wed, 2 Jan 2013 15:20:48 -0800 (PST) X-Received: by 10.236.44.148 with SMTP id n20mr47693642yhb.71.1357168847452; Wed, 02 Jan 2013 15:20:47 -0800 (PST) Return-Path: Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com. [50.56.192.79]) by mx.google.com with ESMTP id u19si20746352anh.133.2013.01.02.15.20.46; Wed, 02 Jan 2013 15:20:47 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 306202E0B2; Wed, 2 Jan 2013 23:20:48 +0000 (UTC) Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by rubyforge.org (Postfix) with ESMTP id 2C8A72E083 for ; Wed, 2 Jan 2013 23:20:30 +0000 (UTC) Received: by mail-vb0-f44.google.com with SMTP id fc26so15119573vbb.3 for ; Wed, 02 Jan 2013 15:20:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=0asdGEOlbJKdSFknLiI9RvBM78Y5uiHk+q07o7jvd2A=; b=GGD0vNe3pOMAM1RJtZeDgTRrQaodpnMq6L1ORIEnxDjPJRf/ehSAO0rFNEO8Iojyki sv+sfhALSdwQSaYuLQ4GdAgedTZ2fQ5sKocIwBBZOZezKZhEmpx5fjFjN14p2PrdgkO6 lDSwqCd9tc9i3rtBTjcWWU9BXyYWPhQWE7jUDSAy6f7hOExX0mp2eHx9tdbeQCWQigwv nK3NHyc9CDeRM9hiCcMm8hhygjrBd6G/pH3fFmr7A1kteHYDt7V0BhiibFayVuuztXMV SdWi/xCBjdsPRYli+9m86mCJehgmMs/a6omA7EP+YL7/SjnO+mJjv+9iXbsLaCTtPqd6 9zRA== MIME-Version: 1.0 Received: by 10.52.66.51 with SMTP id c19mr39141374vdt.123.1357168828243; Wed, 02 Jan 2013 15:20:28 -0800 (PST) Received: by 10.220.150.68 with HTTP; Wed, 2 Jan 2013 15:20:28 -0800 (PST) X-Originating-IP: [209.131.62.145] In-Reply-To: <1357162160-sup-4225@bloovis.org> References: <1357162160-sup-4225@bloovis.org> Date: Wed, 2 Jan 2013 15:20:28 -0800 Message-ID: From: Jonathan Lassoff To: Mark Alexander X-Gm-Message-State: ALoCoQkY6gIolNDoJ4CulxH7M0ttdnHvcCQbDXE8Nxo0XnhnECWsKULhTeyYMl1mqJxYDbkoq7mh Cc: sup-talk Subject: Re: [sup-talk] sup Xapian crash X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Wed, Jan 2, 2013 at 1:33 PM, Mark Alexander wrote: > Excerpts from Jonathan Lassoff's message of Wed Jan 02 15:26:15 -0500 2013: >> I'm having a sad day with sup. I'm crashing with a Xapian error I'll >> have to dig into. > > I've never attempted to debug these kinds of crashes (which I run into > once or twice a year). Instead, I use sup-dump to save the state of > the index, rename .sup/xapian to .sup/xapian.bad, then use sup-sync > --restore to rebuild the index. I started digging, but got bored with reading about the Xapian APIs, so I mostly did what you just did as well :P However, I needed to perform a sup-sync first to create the index and add the messages in, so when I restored from the dump, pretty much everything was marked as unread. Working in the console to declare inbox bankruptcy and inbox zero, and just clearing it all out. Thank goodness I'm starring threads that I need to follow up on! :p > Even though sup is not maintained, I'm so addicted to it that I'm willing > to put up with this inconvenience once in a while. Yeah, I've been using sup for so long that I can't just let it go now. I've got all these excellent hooks and I know the system well. Have you looked at Heliotrope / Turnisole yet? That totally seems like wmorgan's future mail architecture, and I've been curious to migrate to it, but haven't been able to sink the time into it just yet. Cheers, jof _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk