Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
util:sbbsecho [2020/03/10 21:56] – [SCFG] missing closing paren digital man | util:sbbsecho [2022/11/30 13:49] – Remove viewcvs link (no longer valid) digital man | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== SBBSecho ====== | + | ====== SBBSecho |
Synchronet' | Synchronet' | ||
Line 65: | Line 65: | ||
</ | </ | ||
+ | An alternative method is to instead subscribe/ | ||
===== Area File ===== | ===== Area File ===== | ||
Line 317: | Line 318: | ||
Log Timestmap Format defines the format of the date/ | Log Timestmap Format defines the format of the date/ | ||
along with each log message to the log file (e.g. '' | along with each log message to the log file (e.g. '' | ||
- | The timestamp format is defined using standard C '' | + | The timestamp format is defined using standard C '' |
The default format is: '' | The default format is: '' | ||
For SBBSecho v2 timestamp format, use '' | For SBBSecho v2 timestamp format, use '' | ||
Line 771: | Line 772: | ||
from any additionally configured EchoLists which they have | from any additionally configured EchoLists which they have | ||
access to. | access to. | ||
+ | |||
+ | == Zone Blind SEEN-BY and PATH Lines == | ||
+ | Zone Blind SEEN-BY and PATH Lines when Enabled will cause SBBSecho to assume that node numbers are not duplicated across zones and that a net/node combination in either of these Kludge lines should be used to identify a spcific node regardless of which zone that node is located in (thus breaking the rules of FidoNet 3D addressing). | ||
+ | |||
+ | If you are having trouble with FidoNet echomail crossing Zone boundaries which does not add all the SEEN-BY and PATH nodes, then enable this option with the limit of " | ||
=== Paths and Filenames === | === Paths and Filenames === | ||
Line 957: | Line 963: | ||
==== Instances ==== | ==== Instances ==== | ||
- | SBBSecho is designed to run only one instance at a time. A mutual-exclusion file ('' | + | SBBSecho is designed to run only one instance at a time. A mutual-exclusion file ('' |
If you get the following error message (on the console and/or the log file) and you can confirm that SBBSecho is not actually running, you can safely delete the mutex file to allow SBBSecho to again run normally: | If you get the following error message (on the console and/or the log file) and you can confirm that SBBSecho is not actually running, you can safely delete the mutex file to allow SBBSecho to again run normally: | ||
Line 1022: | Line 1028: | ||
Remote area manager, or AreaFix, commands are used by linked nodes in order to | Remote area manager, or AreaFix, commands are used by linked nodes in order to | ||
turn echo areas off and on, list currently connected areas, and more. | turn echo areas off and on, list currently connected areas, and more. | ||
- | The following text is from the file '' | + | The following text is from the file '' |
SBBSecho, should be located in your Synchronet '' | SBBSecho, should be located in your Synchronet '' | ||
area manager commands available to the linked nodes which have been configured using | area manager commands available to the linked nodes which have been configured using | ||
Line 1059: | Line 1065: | ||
==== Changes in Version 3 ==== | ==== Changes in Version 3 ==== | ||
- | |||
- | For a detailed list of changes and code differences introduced in v3.0, see [[http:// | ||
The most major changes introduced in v3.0 are: | The most major changes introduced in v3.0 are: |