From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11048 Path: main.gmane.org!not-for-mail From: Sudish Joseph Newsgroups: gmane.emacs.gnus.general Subject: Re: saving to nnml groups Date: 23 May 1997 13:20:50 -0400 Message-ID: References: <873eresl3p.fsf@perv.daft.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035150823 27975 80.91.224.250 (20 Oct 2002 21:53:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:53:43 +0000 (UTC) Return-Path: Original-Received: from sandy.calag.com (root@sandy [206.190.83.128]) by altair.xemacs.org (8.8.5/8.8.5) with ESMTP id LAA16273 for ; Fri, 23 May 1997 11:16:02 -0700 Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by sandy.calag.com (8.8.5/8.8.5) with ESMTP id LAA32113 for ; Fri, 23 May 1997 11:15:44 -0700 Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id NAA14627 for ; Fri, 23 May 1997 13:15:02 -0500 (CDT) Original-Received: from atreides.eng.mindspring.net (atreides.eng.mindspring.net [207.69.183.11]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Fri, 23 May 1997 19:21:21 +0200 Original-Received: (qmail 386 invoked by uid 52477); 23 May 1997 17:20:50 -0000 Original-To: ding@ifi.uio.no In-Reply-To: Kai Grossjohann's message of 23 May 1997 16:51:07 +0200 X-Mailer: Gnus v5.4.52/XEmacs 20.2 Original-Lines: 29 Original-Xref: altair.xemacs.org dgnus-list:1437 Xref: main.gmane.org gmane.emacs.gnus.general:11048 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11048 Kai Grossjohann writes: > I presume using nnmh will be better because it doesn't have .overview > files, but I don't grok the implications with regard to the active > file. Anyone? The active file gets clobbered routinely if you do asynch delivery. Not A Big Deal, IMO -- the very next message delivered to that group will rectify the problem. When I used asynch delivery, my assumptions were (a) Gnus splitting over NFS was unusable at OSU and (b) that the only important thing was to ensure that you never clobber an actual article. All the rest -- .overview/active files -- are very easy to check and (re)generate. I used to run my nnml-fixer script after quitting Gnus or when my pbiff showed me articles that Gnus didn't (it'd show you the From/Subject headers in any group and even an article, if you selected one). Since pbiff used the atime/mtime kluge (*) to detect new articles, it was impossible for both Gnus and pbiff to miss an article. -Sudish (*) I used a slightly modified version of Joe Hildebrand's perl delivery script. One of the mods was to do the equivalent of "utime +($now = time) - 1, $now, $article;" before exiting. This was sufficient to guarantee that either Gnus or pbiff would see $article -- if pbiff didn't see it, Gnus had to have read it.