Hi there,
I've now got myself an zfs file system so shouldn't have any inode
issues, plus I'm blocking the mixmin server, I hope, by adding
mixmin.com to the cleanfeed bad_paths file.
Now, after I've deleted all the rogue articles, I'm ready to copy my
spool back to the server. This means I'm going to be missing news from somewhere around 15th April until current.
Julien told me that it's possible for newsmasters to resend articles
but it's a manual process and didn't elaborate.
Can someone explain how that would be achieved? for example, to resend everything from Apr 15 at 00:00 GMT.
I'll just have a "ME" line in newsfeeds so the articles wont get sent
out to everyone else until the process is complete.
To be sure, I'll also need to make sure my newsserver doesn't reject
the older articles. Oh man, I feel such a noob! lol.
Thanks,
On Apr 28, 2023 at 10:59:03 AM CDT, "Nigel Reed" <sysop@endofthelinebbs.com> wrote:
Hi there,
I've now got myself an zfs file system so shouldn't have any inode
issues, plus I'm blocking the mixmin server, I hope, by adding
mixmin.com to the cleanfeed bad_paths file.
Now, after I've deleted all the rogue articles, I'm ready to copy my
spool back to the server. This means I'm going to be missing news from
somewhere around 15th April until current.
Julien told me that it's possible for newsmasters to resend articles
but it's a manual process and didn't elaborate.
Can someone explain how that would be achieved? for example, to resend
everything from Apr 15 at 00:00 GMT.
I'll just have a "ME" line in newsfeeds so the articles wont get sent
out to everyone else until the process is complete.
To be sure, I'll also need to make sure my newsserver doesn't reject
the older articles. Oh man, I feel such a noob! lol.
Thanks,
This is the best explanation for what you're after from https://www.eyrie.org/~eagle/faqs/inn.html#S6.4:
To feed all articles on an existing server to another one, regardless of how they're stored on the server, first tell the new server to accept articles regardless of how old they are (otherwise, INN will reject articles older than
artcutoff in inn.conf) and disable your filtering:
ctlinnd param c 0
ctlinnd perl n
ctlinnd python n
In case you wish to only feed articles arrived on the old server between two dates, you can adapt the previous commands with a condition on the $arrived variable (or the $posted variable if you prefer to use the Date header field instead of the actual arrival time). For instance, the following commands will
feed articles arrived between two given timestamps (that can be computed with the convdate utility shipped with INN).
convdate -n '15 Apr 2014 20:42 +0200' '16 Apr 2014 12:37 +0200'
returns the two corresponding timestamps 1397586540 and 1397644620 that can then be used to retrieve a subset of articles to feed:
cd <pathdb in inn.conf>
perl -ne 'chomp; our ($hash, $timestamps, $_) = split " "; \
my ($arrived, $expires, $posted) = split("~", $timestamps); \
print "$_\n" if $_ and $arrived >= 1397586540 \
and $arrived <= 1397644620' history \| tr . / ><pathoutgoing ininn.conf>/list
innxmit server list
Forgot to mention, if you want someone to try feeding you a batch,
hit me up via e-mail.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 60:16:35 |
Calls: | 6,712 |
Files: | 12,243 |
Messages: | 5,355,756 |