Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: [PATCH 0/4] Improve delayer (Christoph Biedl)
2. Re: [PATCH 0/2] More criteria for storage.conf (Christoph Biedl)
3. Re: [PATCH 1/2] storage: Add "filtered" option, to store
based on the filter's decision (Christoph Biedl)
4. INN2 on a Raspberry Pi 4? | Migrating between instances of
INN2 (Avon)
----------------------------------------------------------------------
Message: 1
Date: Mon, 5 Feb 2024 21:38:40 +0100
From: Christoph Biedl <[email protected]>
To: [email protected]
Subject: Re: [PATCH 0/4] Improve delayer
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE wrote...
> Thanks again for your patches. They are now merged upstream.
Sorry for being late, other things in life ... but no worries.
> I've added a sentence about delayer in the manual pages of innfeed and
> newsfeeds, as well as a commented innfeed-delayed! entry in the newsfeeds
> sample.
> Also, I've tried to detail a bit more the manual page of delayer. I hope
> the result is fine. Do not hesitate to speak up in case something needs
> changing.
All is looking good, thanks.
Christoph
------------------------------
Message: 2
Date: Mon, 5 Feb 2024 21:41:31 +0100
From: Christoph Biedl <[email protected]>
To: [email protected]
Subject: Re: [PATCH 0/2] More criteria for storage.conf
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE wrote...
> I totally agree this patch is worthwhile integrating into INN.
> The "filtered" option reminded me something. You already proposed it two
> decades ago :) so it proves to be re-usable for different waves of spam!
> https://github.com/InterNetNews/inn/issues/38
>
> It's now time to integrate it. Thanks for the updated patch against the
> current version!
Eh, completely forgot about that.
> > This path is not shown in the cnfsstat output yet, I felt cnfsstat
> > could use a rewrite in the output formatting. Still I could do a
> > quick-and-dirty solution for the moment, just say the word.
>
> You can do whatever you feel appropriate.
Okay, I'll see what I can do.
> > The patches were developed against the 2.7.1 release, and in use for
> > several weeks.
>
> Not years? :)
> Did you stop using your previous patch?
Oh well, "several weeks" since applying to 2.7.1 :)
The "filtered" patch was indeed in use all the years, on a way older
INN version though (at least it started with a 2). The second one is new.
Christoph
------------------------------
Message: 3
Date: Mon, 5 Feb 2024 21:47:33 +0100
From: Christoph Biedl <[email protected]>
To: [email protected]
Subject: Re: [PATCH 1/2] storage: Add "filtered" option, to store
based on the filter's decision
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE wrote...
> I've gone ahead, and implemented the following rule: if all the storage
> classes have this new filtered key set to false, filtered articles are
> stored in the same storage class as accepted articles. It is only when at
> least one storage class has this key set to true than filtered articles and
> accepted articles are no longer stored mixed together in any storage class.
This seems sane, I read your description as "following the principle of
least surprise". Although I'll need another coffee to think through the
logic here.
Thanks for catching this not-so-corner case which just does not exist in
my installations.
Christoph
------------------------------
Message: 4
Date: Tue, 6 Feb 2024 10:38:13 +1300
From: "Avon" <[email protected]>
To: <[email protected]>
Subject: INN2 on a Raspberry Pi 4? | Migrating between instances of
INN2
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi there
I have been running a INN 2.7.1 server for a number of years on a
Debian system.
The hardware that this runs on a tower PC with a power consumption
I am thinking of mitigating by investigating a shift of the NNTP
server over to a Pi4.
It's been years since I painstakingly set up the current server so
my depth of knowledge is not super fresh on all things INN2.
My thinking is ideally I would also run other projects on the Pi4
as well if doable.
Plans include experimenting with other projects using Docker that
will likely want some of the hardware compute / memory although I
am not overly familiar with Docker or it's level of demands.
Currently the Pi4 has a new install of the latest Bookworm
Raspberry Pi OS, it boots from a 250 Gig SSD and has 8 gig of
memory.
Pi4 questions
Can I run INN2 on the Pi4?
What amount of compute / memory resources do I need to allow for
INN2 if I were to run it on a Pi4?
Should I be using the APT manager to install INN2 and if so which
package, or am I better off to just build the software from the
source files like I did last time on my Debian box?
Anything Pi specific I should be aware of / wary of?
INN2 questions
I run mostly CNFS buffers to store my articles, can I move them
over to the new server I install on the Pi4? Total data is
currently 82.7 Gig. Picking not as a direct copy and CNFS data is
the hardest to transfer over?
In thinking about some info I read on how to send articles from
one server to another. If I want my new server to use the same
domain name as my old server etc. (what shows in the path) is
there anyway to transfer articles over from one system to the
other like that?
Has anyone tried running/using INN2 with Docker?
There's probably more questions rattling around in my head but
thanks for any and all thoughts / feedback.
Best, Paul (news.bbs.nz)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 158, Issue 1
*******************************************