From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.182.92.230 with SMTP id cp6csp574490obb; Wed, 2 Jan 2013 13:40:26 -0800 (PST) X-Received: by 10.236.151.68 with SMTP id a44mr46049395yhk.59.1357162825645; Wed, 02 Jan 2013 13:40:25 -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 f27si31949998yhn.53.2013.01.02.13.40.25; Wed, 02 Jan 2013 13:40:25 -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 2FA5D2E0AB; Wed, 2 Jan 2013 21:40:26 +0000 (UTC) X-Greylist: delayed 382 seconds by postgrey-1.31 at rubyforge; Wed, 02 Jan 2013 21:40:10 UTC Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by rubyforge.org (Postfix) with ESMTP id C9BEC2E084 for ; Wed, 2 Jan 2013 21:40:10 +0000 (UTC) Received: by mail-pb0-f41.google.com with SMTP id xa7so8134640pbc.0 for ; Wed, 02 Jan 2013 13:40:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:content-type:cc:subject:from:to:in-reply-to :references:date:message-id:user-agent:content-transfer-encoding; bh=e86uytk08IMUSiyiw6JOWlT4Ri52gK/YPNPyJiLKj0Q=; b=hT8V6NeuNkUctB4K71DTbq/uNU/E3Rt/WaUeAYNfyY5jjqQlAZXLcrKJsZrgCtoUd4 nGY9UMlH03efX6WT2m+4UJ7zoBJCHRw/AgwBPR2d329Sszo/30dWJBFNodW11NA8dZNB T4wR8HaNxxo3YaSNB7GjOY2kuUadXfOsGobscfJqICZJyI/rFdX7NTzDAxlfDHmloF/l xXH7RdgXFRlTQngaVzhCkJrtw7hL2zBs5Nwho9b1wuLRU/7m2Hx1LZmyosWJMCotLBUg 3yDAmRhQQ/RwNcx7XKqWaSaRDnDk4XohvuEqI2sq0UW3pWE5vFgqWs+KqGoXOvUG2myY YqdA== X-Received: by 10.66.89.9 with SMTP id bk9mr139205615pab.67.1357162423781; Wed, 02 Jan 2013 13:33:43 -0800 (PST) Received: from localhost (c-76-19-84-172.hsd1.vt.comcast.net. [76.19.84.172]) by mx.google.com with ESMTPS id se4sm29032397pbb.13.2013.01.02.13.33.41 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Jan 2013 13:33:42 -0800 (PST) From: Mark Alexander To: Jonathan Lassoff In-reply-to: References: Date: Wed, 02 Jan 2013 16:33:39 -0500 Message-Id: <1357162160-sup-4225@bloovis.org> User-Agent: Sup/git 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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. 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. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk