Received: with ECARTIS (v1.0.0; list gopher); Sat, 31 Dec 2005 12:47:26 -0600 (CST) Received: from mo-69-69-114-6.sta.sprint-hsd.net ([69.69.114.6] helo=erwin.lan.complete.org) by glockenspiel.complete.org with esmtps (with TLS-1.0:RSA_AES_256_CBC_SHA:32) (TLS peer CN erwin.complete.org, certificate verified) (Exim 4.50) id 1EsllD-0000Of-Hw; Sat, 31 Dec 2005 12:47:26 -0600 Received: from katherina.lan.complete.org ([10.200.0.4]) by erwin.lan.complete.org with esmtps (with TLS-1.0:RSA_AES_256_CBC_SHA:32) (No TLS peer certificate) (Exim 4.50) id 1Esll5-0005Z8-Qw; Sat, 31 Dec 2005 12:47:15 -0600 Received: from jgoerzen by katherina.lan.complete.org with local (Exim 4.60) (envelope-from <jgoerzen@katherina.lan.complete.org>) id 1Esll5-0005ed-MH; Sat, 31 Dec 2005 12:47:15 -0600 Date: Sat, 31 Dec 2005 12:47:15 -0600 From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Subject: [gopher] Gopher archive bot running again Message-ID: <20051231184715.GA21724@katherina.lan.complete.org> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Spam-Status: No (score 0.1): AWL=0.008, FORGED_RCVD_HELO=0.05 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Sat, 31 Dec 2005 12:47:26 -0600 Content-Transfer-Encoding: 8bit X-archive-position: 1210 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

Hi folks,

I never found the problem that was causing gopherbot to segfault before, but I did trace it down to the database toolkit I was using. I had several other complaints with that toolkit, so I set about writing my own (see gopher://gopher.quux.org/1/devel/hdbc). It's now ready for use and I've ported gopherbot to it. Everything's working well, so the sites that weren't fully cached before will see some hits.

-- John