From: Harry Putnam <reader@newsguy.com>
Subject: Re: Virtual server/major confusion
Date: 31 Oct 1999 17:01:22 -0800 [thread overview]
Message-ID: <m3emebqb31.fsf@satellite.local.lan> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "01 Nov 1999 01:21:59 +0100"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > Still pressing "g" on n2m server doesn't generate nov files.
>
> Hm. Does M-x nnml-generate-nov-databases RET help?
Yes...I have .overview files now
>
> > {nnml:n2m} (closed)
> > {nnml:n2m} (opened)
> >
> > The groups have now appeared in "group" buffer, but they still don't
> > have nov files.
> >
> > Seems like lots of crazy behavior for something that should be kind of
> > easy to do.
>
> Hm. Maybe one of the servers is secondary, and the other is foreign?
> Does the .newsrc.eld file contain one of the servers?
One appears in .newsrc.eld along with the n2m groups:
("n2m" nnml "n2m" (nnml-directory "/mnt/bak/n2m/") (nnml-active-file "/mnt/bak/n2m/active"))))
> Please generate the NOV files and then copy and move around articles
> to see if the NOV files are kept up to date. Depending on how the
> articles got into the server, I can understand NOV problems (you did
> have the wrong file name in the parameters), but once that's cleared
> up, the NOV data should be kept up to date automatically. If it
> isn't: maybe a bug?
After moving a few files around and seeing the nov files keep pace and
another restart I now have a single n2m server in server buffer and
all seems to be hunky dory.
Thanks again Kai
prev parent reply other threads:[~1999-11-01 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-31 18:03 Harry Putnam
1999-10-31 22:33 ` Kai Großjohann
1999-10-31 23:31 ` Harry Putnam
1999-11-01 0:21 ` Kai Großjohann
1999-11-01 1:01 ` Harry Putnam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3emebqb31.fsf@satellite.local.lan \
--to=reader@newsguy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).