MSGID: 1:154/10 664698ec
REPLY: 4:801/188 ae14d4f0
PID: SmapiNNTPd/Linux 2.4.6
CHRS: UTF-8 4
TZUTC: -0500
TID: hpt/lnx 1.9 2024-02-05
On Thu, 16 May 2024 16:45:28 -0300, Flavio Bessa -> All wrote:

 FB> I am going through the .ctl file configuration, but I am stuck now at
 FB> the final section of the file:

 FB> ; Your region source data goes here.

Under data, that would be your RC entry for the nodelist.

 FB> Node   ; node files must precede any network
files
 FB> Node   ; (unless it is your intent to move an
 FB>                                 ;  independant node into someone's net on
 FB>                                 ;  on the sly)

These would be your RIN nodes.

 FB> Net       ; either generic or explicit file name, but must
 FB> Net       ; match convention used by Net.
 FB> Net    ; if not "net/0"
 FB> Net  
 FB> ;      etc.

These are your nets. The  would basically be an include file if you
get net segments sent to you, or even if you keep your nets in separate files.

 FB> Would anyone have any examples that I could find? This is to automate
 FB> the maintenance of my R80.

data

Region,11,Midwest_USA,Pewaukee_WI,Nicholas_Boel,-Unpublished-,30
,CM,INA:binkp.pharcyde.org,IBN

files

net 104 net104.txt
net 114 net114.txt
net 120 net120.txt
net 128 net128.txt
net 154 net154.txt
net 220 net220.txt
net 226 net226.txt
net 227 net227.txt
net 2320 net2320.txt

There is a fairly plain example. I have NCs who send their segments to me as
the filenames listed above. When they're detected in my inbound by binkd,
they're moved to the "received" directory for makenl, and with the above
settings makenl will know to process those files if they reside in the
'received' directory.

Once makenl is done, the 'data' line, along with all of the files below the
'files' line are appended together into one file, region11.xxx.

Hope that helps!

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
SEEN-BY: 90/1 103/705 105/81 106/201 123/10 124/5016 128/260 129/305
SEEN-BY: 135/220 225 153/757 7715 154/10 30 40 50 700 203/0 218/700
SEEN-BY: 220/90 221/0 6 226/30 227/114 229/110 112 113 206 317 426
SEEN-BY: 229/428 470 664 700 705 240/1120 5832 266/512 280/464 5003
SEEN-BY: 282/1038 291/111 292/854 8125 301/1 310/31 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 423/120 460/16 58 256 1124 5858
SEEN-BY: 467/888 633/280 712/848 770/1 2320/105 3634/12 5020/400 5054/30
SEEN-BY: 5075/35
PATH: 154/10 280/464 460/58 229/426