On 28/01/2024 05:25, Nigel Reed wrote:
>
> With cnfs there's no need to worry about those newsgroup name issues,
> but there's no easy direct method of viewing the articles.
You need to know the token, but it's easy with m-id. You can grab the
tokenname with grephistory, and then read the article with sm. It's just
a step + 1 to read, and not pointing directly the article into the
filesystem.
> I also fear that I will lose articles if, for some how, the buffers get
> full and start to overwrite without me noticing it.
>
Actually I'm setup 2 new newsserver, and grabbing news from various
source with cnfs and buffindexer without big trouble. The only defect
it's the harddisk space it's areally taken.
> Also, will space from expired or canceled articles be reused or does
> that usually get reclaimed when the buffer recycles? I could end up
> losing a lot of space.
>
> Also, if using cnfs, would would be the best way to create the buffers?
> I have a 1.9TB block of space that I can keep as a single partition or
> divvy up into multiple.
>
> After advise from those more in the knowledge of cnfs than me
>
> Thanks,
> Nigel
>
See INSTALL file from inn2 tarball, section "Creating the Article Spool
(CNFS only)" or
mkbuf.in file in CONTRIB section. In my case I have do a
little rewrite them for daily use, and it's the "easy way" to create a
new one cyc buff and adding them to storage.conf file. I use a file into
directory /var/spool/news/cycbuff (same filesystem ad /, but you can do
a new partition for this with different filesystem).
For warning when a cyc buff it's "full" I have created a script, added
in crontab, running cnfsstat -a, when the value of cycles reach *.80
send me an email and my system create in auto a new cyc buffer with
predefined space, add it into storage.conf (using the pattern in Class
readed with cnfsstat), and reload inn2. But in my case I have 24TB of
diskspace, and create a new cyc it's not hard for me.
In your case with only 2TB of space I recommend you create some small
cycs for those groups (or hierarchies) that are not important to you and
which can also expire quickly and suppose 50/500MB it's enought for
control.* or *.test, and some "large" cycs for the groups (or
hierarchies) that instead you want to maintain, in that case 1/10GB. If
you set as sequential, not big trouble, and easy to reuse (or backup)
and you can set a good retention for everything's.
The stats of my newsserver (text only) it's a retention from '90/2000
take 4/5TB of space. A lot of group have millions of post (one I have
see have 20 millions, impossible to grep all with normal newsreader).
Sincerely
--
Ivo Gandolfo