Has anyone been having problems compiling nodelists? I do not have a nodelist.dat or anything close to it in my data directory thus my nodelist application is not working.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Moderate Chaos (21:2/149)

On 19 Jul 2019, modchaos said the following...

Has anyone been having problems compiling nodelists? I do not have a nodelist.dat or anything close to it in my data directory thus my
nodelist application is not working.

Is there an ini file setup for processing the nodelists and are the lists present in the system? The line for mutil in my system looks like: [MergeNodeLists]


; Strip nodes marked as DOWN?
strip_down = true

; Strip nodes marked as PRIVATE?
strip_private = false

nodefile=/mystic/files/fsx_node/fsxnet
nodefile=/mystic/files/rtn_nodelist/retronet

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 19 Jul 2019, modchaos said the following...

Has anyone been having problems compiling nodelists? I do not have a nodelist.dat or anything close to it in my data directory thus my
nodelist application is not working.

To make it easier here's the whole .ini I use:
; maint.ini for Mystic Pi BBS bcw142.zapto.org
; from omutil.ini (Original mutil.ini)
;
; Purge, pack & merge nodelists
;
[General]

MergeNodeLists = true
logfile=mutil.log
loglevel=3
maxlogfiles = 3
maxlogsize = 1000

; ==========================================================================
; ==========================================================================

[MergeNodeLists]


; Strip nodes marked as DOWN?
strip_down = true

; Strip nodes marked as PRIVATE?
strip_private = false

nodefile=/mystic/files/fsx_node/fsxnet
nodefile=/mystic/files/rtn_nodelist/retronet

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

Is there an ini file setup for processing the nodelists and are the lists present in the system? The line for mutil in my system looks like: [MergeNodeLists]
; Strip nodes marked as DOWN?
strip_down = true

; Strip nodes marked as PRIVATE?
strip_private = false

nodefile=/mystic/files/fsx_node/fsxnet
nodefile=/mystic/files/rtn_nodelist/retronet

Yes I actually have this as part of my maint nightly.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Moderate Chaos (21:2/149)

Funny part is the MUTIL output shows that it processed three nodelists BUT no data file is written in the data directory that I can see.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Moderate Chaos (21:2/149)

On 19 Jul 2019 at 08:43p, modchaos pondered and said...

Funny part is the MUTIL output shows that it processed three nodelists
BUT no data file is written in the data directory that I can see.

The file will be called nodelist.txt and should sit in the data directory.

If you run the merge nodelist stanza what do level 3 logs from Mutil show?

.. just check you have unzip installed :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

If you run the merge nodelist stanza what do level 3 logs from Mutil
show?

Why yes - I found the answer switching to Debug. MUTIL will report is
processed a nodelist even though it does not find a nodelist file. I would assume this is to be expected in case there is no nodelist file.

In any case, I was specifying the nodelist directories in my INI and MUTIL
was looking for the nodelist file name to start with the name of what I
thought was the last directory.

I now have a nodelist.txt file in my data directory.

Thanks,
D

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Moderate Chaos (21:2/149)

On 21 Jul 2019 at 01:19a, modchaos pondered and said...

Why yes - I found the answer switching to Debug. MUTIL will report is

cool

In any case, I was specifying the nodelist directories in my INI and
MUTIL was looking for the nodelist file name to start with the name of what I thought was the last directory.

OK so you were missing say the very last bit in the nodefile line then?
like a fsxnet for the nodelist name to look for?

e.g. nodefile=c:\mystic\files\fsx\fsx_node\fsxnet

I now have a nodelist.txt file in my data directory.

Yay, well done for sussing it out.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)