Ben Rosengart | 1 May 01:46 2002
Picon

how does nnrpdposthost work?


If one host, call it foo, has "nnrpdposthost: bar" set, what protocol
is used between foo and bar when someone posts through foo's nnrpd?

I'm curious about the whole thing, but the immediate motivation is to
find out which host needs to have an up-to-date moderators file.

--

-- 
Ben Rosengart     (212) 741-4400 x215

1. A robot may not injure entertainment industry profits, or, through inaction,
   allow entertainment industry profits to come to harm.     --Matt McLeod

Katsuhiro Kondou | 1 May 13:40 2002

Re: how to determine size of local.* hierarchy


In article <3CCDB194.25C5B777 <at> mitre.org>,
	Steven Sesar <ssesar <at> mitre.org> wrote;

} Someone just asked me how to determine the size of our local.* hierarchy, and I realized that I have no idea.
We are storing articles using CNFS, and don't have the local* hierarchy pointing to any specific place, so
cnfsstat isn't very helpful.

I can't imagine handy method to do that.  If you don't
mind doing more, sum of bytes entry returned by 'xover
lo-hi' could give it.
--

-- 
Katsuhiro Kondou

Rob Morin | 1 May 15:39 2002
Picon

what does this mean...

should i worry.....

expireover: could not expire control
expireover: could not expire control.cancel
expireover: could not expire control.newgroup
expireover: could not expire 24hoursupport.helpdesk
expireover: could not expire ab.forsale
expireover: could not expire alt.abortion
expireover: could not expire alt.bible
expireover: could not expire alt.comp.freeware
expireover: could not expire alt.dss.hack
expireover: could not expire alt.fan.italian.anime.dragonball
expireover: could not expire alt.gossip.celebrities
expireover: could not expire alt.politics
expireover: could not expire fr.soc.politique
expireover: could not expire news.lists.filters
expireover: could not expire rec.games.pinball
expireover: could not expire rec.sport.disc
expireover: could not expire rec.sport.unicycling
expireover: could not expire soc.culture.israel
expireover: could not expire talk.politics.misc
expireover: could not expire tw.bbs.literal.emprisenovel
expireover: could not expire tw.bbs.rec.car
expireover: could not expire uk.local.cumbria
expireover: could not expire uk.politics.misc
expireover: could not expire uk.rec.audio
expireover: could not expire pl.rec.foto
expireover: could not expire it.discussioni.leggende.metropolitane
expireover: could not expire fr.reseaux.telecoms.adsl
expireover: could not expire alt.nocem.misc
(Continue reading)

Jeffrey M. Vinocur | 1 May 17:11 2002

Re: how does nnrpdposthost work?


On Tue, 30 Apr 2002, Ben Rosengart wrote:

> If one host, call it foo, has "nnrpdposthost: bar" set, what protocol
> is used between foo and bar when someone posts through foo's nnrpd?

IIRC, the remote host must have an appropriate listing in incoming.conf, 
which implies that the peering (IHAVE) mechanism is used.

--

-- 
Jeffrey M. Vinocur
jeff <at> litech.org

Ben Rosengart | 1 May 17:15 2002
Picon

Re: how does nnrpdposthost work?


On Wed, May 01, 2002 at 11:11:41AM -0400, Jeffrey M. Vinocur wrote:
> On Tue, 30 Apr 2002, Ben Rosengart wrote:
> 
> > If one host, call it foo, has "nnrpdposthost: bar" set, what protocol
> > is used between foo and bar when someone posts through foo's nnrpd?
> 
> IIRC, the remote host must have an appropriate listing in incoming.conf, 
> which implies that the peering (IHAVE) mechanism is used.

This implies in turn that moderation is handled on host "foo"?

--

-- 
Ben Rosengart     (212) 741-4400 x215

1. A robot may not injure entertainment industry profits, or, through inaction,
   allow entertainment industry profits to come to harm.     --Matt McLeod

Tommy van Leeuwen | 1 May 19:26 2002
Picon

Re: SERVER cant dbzinit /usr/local/news/db/history Numerical argument out of domain


Hi,

I've got this message once on Linux after i reconfigured with
--with-largefiles so it's probably a datastructure messed up in your
history or so. inn wouldn't start at all and back to the old config
everything worked ok again.

Have you tried regenerating your history? Have any system libraries been
updated since you've got this message? I think regenerating history would
fix this problem (wild guess).

Regards,
Tommy

On Mon, 29 Apr 2002, Rob Morin wrote:

> Hello anyone know what this can mean?
>
> I am running INN 2.3.2 on Freebsd 4.5
>
> i get this about 5 or 6 times a day... my disk are not full and my overview is ok...
>
> what can it be or what is it?
>
> after i shutdown and restart INN it works ok for a while...
>
>
> Rob Morin(Mr.Legacy)
> System Administrator
(Continue reading)

Bill Tangren | 1 May 19:59 2002
Picon

retrieving expired messages


Hi all,

I am running inn 2.3.2-5, and I had left the expire settings, on one of 
my newsgroups, set to the default, and what I wanted was for them not to 
expire at all. I have made the requisite changes to expire.ctl, and I 
have the expired messages on backup tape. How do I retrieve them? I 
think that renumbering and history file are the big problems. Any ideas 
how to do this, or where to read up on how to do it?

Bill Tangren

Wim Lewis | 1 May 21:21 2002

Re: retrieving expired messages


On Wednesday, May 1, 2002, at 10:59  AM, Bill Tangren wrote:
> I am running inn 2.3.2-5, and I had left the expire settings, on one of
> my newsgroups, set to the default, and what I wanted was for them not to
> expire at all. I have made the requisite changes to expire.ctl, and I
> have the expired messages on backup tape. How do I retrieve them? I
> think that renumbering and history file are the big problems. Any ideas
> how to do this, or where to read up on how to do it?

Are you using tradspool? I don't think renumbering is a problem; INN 
doesn't tend to reuse article numbers. (That would confuse most news 
clients.) You should be able to restore the article files to the spool 
directory, adjust the group's low article number in 'active', and 
rebuild the overview database. (I don't know if rebuilding history is 
also necessary.) See the man page for makehistory(8) (which also does 
the overview databases).

Wim.

Russ Allbery | 2 May 00:00 2002
Picon

Re: how does nnrpdposthost work?


Ben Rosengart <br+inn <at> panix.com> writes:
> On Wed, May 01, 2002 at 11:11:41AM -0400, Jeffrey M. Vinocur wrote:
>> On Tue, 30 Apr 2002, Ben Rosengart wrote:

>>> If one host, call it foo, has "nnrpdposthost: bar" set, what protocol
>>> is used between foo and bar when someone posts through foo's nnrpd?

>> IIRC, the remote host must have an appropriate listing in
>> incoming.conf, which implies that the peering (IHAVE) mechanism is
>> used.

> This implies in turn that moderation is handled on host "foo"?

Right.

--

-- 
Russ Allbery (rra <at> stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.

Katsuhiro Kondou | 2 May 02:20 2002

Re: overview strangeness


In article <20020430185414.B292F26E25 <at> boredom.ennui.org>,
	rone <at> ennui.org (figmentality) wrote;

} information, which leads to header-article mismatch.  Should i upgrade
} to the latest -stable?

It may help.  Someone on the list reported this problem,
and I was given the article spool, but it worked for me.
Very weird.  It'd be helpful to trace by gdb.
--

-- 
Katsuhiro Kondou


Gmane