config_system_paths
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
config_system_paths [2016/09/03 19:43] – avon | config_system_paths [2016/09/19 02:11] – content updates avon | ||
---|---|---|---|
Line 45: | Line 45: | ||
=== Semaphore Path === | === Semaphore Path === | ||
+ | |||
+ | The semaphore path is the directory where Mystic BBS creates semaphores as messages are sent or received by the BBS. These semaphores are 0kb files that the Events system can take advantage of to trigger actions to process incoming or outgoing messages as it finds them in this directory. Once messages are imported or exported the semaphore is removed. | ||
=== Menu File Path === | === Menu File Path === | ||
+ | |||
+ | The menu file path is the default directory where Mystic BBS will store it's menu data files. | ||
=== Text File Path === | === Text File Path === | ||
+ | |||
+ | |||
+ | The textfile path is the default directory where Mystic BBS will store it's ANSI (.ANS) and ASCII (.ASC) files along with a number of configuration files (.INI) for the likes of the file index reader, message editor etc. | ||
=== Script Path === | === Script Path === | ||
Line 55: | Line 62: | ||
=== Inbound EchoMail === | === Inbound EchoMail === | ||
+ | |||
+ | The directory where inbound netmail / echomail packets received by BinkP, FTP or Directory sessions from known Echomail Nodes are stored. If received during a Fidopoll session from known Echomail Nodes are also stored in this directory. | ||
=== Inbound EchoMail Unsecured === | === Inbound EchoMail Unsecured === |
config_system_paths.txt · Last modified: 2022/09/26 02:26 by avon