User Tools

Site Tools


mutil_merge_node_lists

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mutil_merge_node_lists [2016/03/29 04:38] avonmutil_merge_node_lists [2016/03/29 04:45] (current) avon
Line 1: Line 1:
 ====== Merge nodelists in to Mystic format ====== ====== Merge nodelists in to Mystic format ======
  
-The '[MergeNodeLists]' stanza instructs MUTIL to find the latest nodelists available in your Mystic system for the various message networks your BBS may be connected to. +The '[MergeNodeLists]' stanza instructs MUTIL to find the latest nodelists available in your Mystic system for the various message networks your BBS is connected to.
  
-After examining all the available nodelists for each message network MUTIL then merges the results together in to a nodelist.txt file that is saved in the Mystic DATA directory.+MUTIL then merges the results together in to a file that can be used by BBS users to look up members of any given message network and send addressed Netmail to them from your BBS.
  
 To enable this function you modify the '[general]' stanza as follows: To enable this function you modify the '[general]' stanza as follows:
- 
  
   [general]   [general]
Line 12: Line 11:
   MergeNodeLists       = true   MergeNodeLists       = true
      
-To do this you need to define a 'nodefile' statement for each message network carried by your Mystic BBS. There must be one 'nodefile' statement per network, per line. The nodefile value must contain the full path and the base filename of the nodelist used by any given message network.+To configure the '[MergeNodeLists]' stanza  you must define a 'nodefile' statement for each message network carried by your Mystic BBS. There may be only one 'nodefile' statement per message network, per line. The nodefile value must contain the full path and the base filename of the nodelist used by any given message network.
  
 Here's an example. Here's an example.
Line 29: Line 28:
 After decompressing, the 3-digit day extensions are compared, selecting the highest number.  It will also compare the years of the file dates, and select the newest option.  So if you have nodelist.025 dated 2013 and also nodelist.320 dated 2012, nodelist.025 will be selected. After decompressing, the 3-digit day extensions are compared, selecting the highest number.  It will also compare the years of the file dates, and select the newest option.  So if you have nodelist.025 dated 2013 and also nodelist.320 dated 2012, nodelist.025 will be selected.
  
-The same process is then be repeated for the fsxnet.### nodelist and then again for the agoranet.### nodelist. Once all of the defined 'nodefiles' are processed, they will be merged together and copied in to Mystic's DATA directory.+The same process is then be repeated for the fsxnet.### nodelist and then again for the agoranet.### nodelist. Once all of the defined 'nodefiles' are processed, they will be merged together and copied to the file nodelist.txt located in Mystic's DATA directory.
  
 If no nodelists are found, Mystic will not overwrite the current nodelist.  Comments are stripped while merging to lower filesize and increase search performance. If no nodelists are found, Mystic will not overwrite the current nodelist.  Comments are stripped while merging to lower filesize and increase search performance.
 +
 +The stanza contains a couple of Boolean switches that can be enabled or disabled. 
  
   ;Strip nodes marked as DOWN?   ;Strip nodes marked as DOWN?
mutil_merge_node_lists.txt · Last modified: 2016/03/29 04:45 by avon

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki