Maybe reporting the value of "artcutoff" in log and INNReport
would be a nice thing.
I still intend to backfill a number of my groups, I'm just nervous
about propagating old articles while still being able to receive and
send new ones.
Hi Nigel,
I still intend to backfill a number of my groups, I'm just nervous
about propagating old articles while still being able to receive and
send new ones.
Did you try to add a fake hop when using pullnews? (-F flag)
https://www.eyrie.org/~eagle/software/inn/docs/pullnews.html
"""
In case you have running peers and don't want to propagate them the
articles you are pulling from upstream servers, you should add a fake
hop with the -F flag to all the pulled articles, and add that very fake
hop in the exclusion sub-field of all the sites configured in your
newsfeeds file. (For example, using "pullnews -F myserverimported",
change "sitename:*:Tm:innfeed!" to
"sitename/myserverimported:*:Tm:innfeed!" for every sitename in
newsfeeds you don't want to feed the pulled articles to.)
"""
This way, you will never be nervous again when running pullnews :-)
P.-S.: If someone has a better or quicker way to prevent pulled articles
from being sent to peers, please tell, and I'll update the pullnews documentation accordingly.
I don't know whether suck has a similar facility.
[...]I don't know whether suck has a similar facility.
With suck you need to use the post filter function.
# find the line and change it
foreach $line ( @file) {
if ( $line =~ /^Path: /) {
$line =~ s/^Path: /Path: myhost\!/
}
}
Maybe reporting the value of "artcutoff" in log and INNReport
would be a nice thing.
It already is at the beginning of the daily report, in a cryptic form :)
Server status:
Server running
Allowing remote connections
Parameters c 10 i 50 (18) l 600000 o 1010 t 300 H 2 T 60 X 0 normal
specified
It is "c 10", the value of the cutoff parameter.
Hi Nigel,
I still intend to backfill a number of my groups, I'm just nervous
about propagating old articles while still being able to receive and
send new ones.
Did you try to add a fake hop when using pullnews? (-F flag)
https://www.eyrie.org/~eagle/software/inn/docs/pullnews.html
"""
In case you have running peers and don't want to propagate them the
articles you are pulling from upstream servers, you should add a fake
hop with the -F flag to all the pulled articles, and add that very
fake hop in the exclusion sub-field of all the sites configured in
your newsfeeds file. (For example, using "pullnews -F
myserverimported", change "sitename:*:Tm:innfeed!" to "sitename/myserverimported:*:Tm:innfeed!" for every sitename in
newsfeeds you don't want to feed the pulled articles to.)
"""
On Sun, 21 Jan 2024 11:27:39 +0100
Julien ÉLIE <iulius@nom-de-mon-site.com.invalid> wrote:
Hi Nigel,
I still intend to backfill a number of my groups, I'm just nervous
about propagating old articles while still being able to receive and
send new ones.
Did you try to add a fake hop when using pullnews? (-F flag)
https://www.eyrie.org/~eagle/software/inn/docs/pullnews.html
"""
In case you have running peers and don't want to propagate them the
articles you are pulling from upstream servers, you should add a fake
hop with the -F flag to all the pulled articles, and add that very
fake hop in the exclusion sub-field of all the sites configured in
your newsfeeds file. (For example, using "pullnews -F
myserverimported", change "sitename:*:Tm:innfeed!" to
"sitename/myserverimported:*:Tm:innfeed!" for every sitename in
newsfeeds you don't want to feed the pulled articles to.)
"""
To be clear, I only need to do this with my peer connections right, not
ME or inpath or innfeed, controlchan etc.
news.bbs.nz/news.bbs.nz,nomilktodaythankyou\
:*,@*.bina*,@*.bain*,@*.dateien*,@*.pictures*,$LOCAL\
:Ap,Tm:innfeed!
I've added "nomilktodaythankyou" to all my peers, similar to this. and
will use -F nomilktodaythankyou when using pullnews so I guess this is
fair warning to my peers :)
Now, who has a 10 year backlog of the soc.* I can slurp for practice? :)
Anyone is free to suck/pull from my server: news.blueworldhosting.com
Big8 hierarchies go back 20-30 years depending on the group.
Reading is open on 119 or 563 via TLS.
Hi,
Jesse Rehmer a tapoté :
Anyone is free to suck/pull from my server:
news.blueworldhosting.com
Big8 hierarchies go back 20-30 years depending on the group.
Reading is open on 119 or 563 via TLS.
Maybe it is in the faq or in the history of news.software.nntp but
how simply sorting by date the articles?
The old posts sucked will be showned at first to NNRP client?
Or creating an old.* local hierarchie to show this olds posts?
To be clear, I only need to do this with my peer connections right, not
ME or inpath or innfeed, controlchan etc.
how simply sorting by date the articles?
The old posts sucked will be showned at first to NNRP client?
Or creating an old.* local hierarchie to show this olds posts?
Salut Stéphane,
how simply sorting by date the articles?
The old posts sucked will be showned at first to NNRP client?
That's how article numbers work, indeed. They increment when a new
article arrives. Old posts will then have a higher article number
than your current articles in the newsgroup.
You'll then have to renumber your newsgroups, which can be done by re-feeding your spool to a fresh new instance. Naturally, the
re-feed is done by article posting date, so that they arrive in order.
You may find useful information in the "Renumber newsgroups by post
date" thread in news.admin.peering in April 2023 (<7Qb1M.3786652$nwq3.3523857@fx13.ams4>).
Is thre no way to renumber a group without having to feed to another
news server? You'd think there'd be a script to do that or something.
Hi Nigel,
To be clear, I only need to do this with my peer connections right,
not ME or inpath or innfeed, controlchan etc.
You should do that for your outgoing peers and I think the inpaths!
entry too so as not to send stats to the top1000 project about your donwloaded articles.
Other entries do not need the exclusion.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 73:00:51 |
Calls: | 6,714 |
Calls today: | 2 |
Files: | 12,246 |
Messages: | 5,357,085 |