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 <nbr> <explicit file name> ; node files must precede any network files
FB> Node <nbr> <explicit file name> ; (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 <nbr> <file name> ; either generic or explicit file name, but must
FB> Net <nbr> <file name> ; match convention used by Net.
FB> Net <nbr> <file name> <notification address> ; if not "net/0"
FB> Net <nbr> <file name>
FB> ; etc.
These are your nets. The <file name> 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-,300,CM,INA:binkp.p
harcyde.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)
|
