Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
util:sbbsecho [2020/03/10 21:54] – [Configure] be more helpful digital man | util:sbbsecho [2020/03/11 14:57] – [EchoList] Mention the badareas.lst import scheme. digital man | ||
---|---|---|---|
Line 65: | Line 65: | ||
</ | </ | ||
+ | An alternative method is to instead subscribe/ | ||
===== Area File ===== | ===== Area File ===== | ||
Line 181: | Line 182: | ||
=== Inbound File Directory === | === Inbound File Directory === | ||
- | Older versions of SCFG (e.g. v3.16) contained this FidoNet setting which was used to specify the directory where non-secure inbound FidoNet files would be received by your FTN mailer. SBBSecho v2 used this setting, however Synchronet itself did not, so it was deprecated with SBBSecho v3 (replaced with the '' | + | Older versions of SCFG (e.g. v3.16) contained this FidoNet setting which was used to specify the directory where non-secure inbound FidoNet files would be received by your FTN mailer. SBBSecho v2 used this setting, however Synchronet itself did not, so it was deprecated with SBBSecho v3 (replaced with the '' |
Line 957: | Line 958: | ||
==== 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: |