From owner-freebsd-questions Wed Dec 30 16:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24362 for freebsd-questions-outgoing; Wed, 30 Dec 1998 16:37:18 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24354 for ; Wed, 30 Dec 1998 16:37:15 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id TAA21864; Wed, 30 Dec 1998 19:48:28 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19981230194242.01b3d9c0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 30 Dec 1998 19:42:42 -0500 To: The Hermit Hacker From: Mike Tancsa Subject: Re: DNEWS on STABLE anyone ? Cc: questions@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:52 PM 12/30/98 -0400, The Hermit Hacker wrote: >On Wed, 30 Dec 1998, Steve Hovey wrote: > >> When we went up in INN it puked too - I run dnews on a 2.2.5, or 2.2.7 - I >> forget which.. Runs like a charm! > > What sort of problems did both/either of you see with INN 2.x? Corrupted spools and databases. Articles that would go missing that should be there. Judging by the threads on news.software.nntp, its still a product in development. The other appeal for me is that the the configuration and documentation seem a little more complete/basic so I can pass off the job to some of our more junior techs. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message