On 11/28/17, Jeffs said the following...
The only possible change I could see is if a keyword could be used on the MUTIL commandline that would cause MUTIL to only use a particular
section of the mutil.in file. As in:
./mutil merge mutil.ini
Which would cause MUTIL to read the [MergeNodelists] section of the mutil.ini file. But I just may be overthinking things. :-) That that exists works fine.
Most of us would create a merge.ini for that. In my case I called it nodelist.ini:
; nodelist.ini for Mystic Pi BBS bcw142.zapto.org
; from omutil.ini (Original mutil.ini)
;
; Purge, pack & merge nodelists
;
[General]
MergeNodeLists = true
logfile=mutil.log
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/fsx_node/fsxnet
nodefile=/mystic/files/rtn_nodelist/RETRONET
nodefile=/mystic/files/rtn_nodelist/retronet
----------------------------------------------------------------------------- So ./mutil nodelist.ini does it and I can use DD (under Linux) to run it from
a menu item so anyone can update the nodelist live on the BBS.
--- Mystic BBS v1.12 A36 2017/11/23 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)