Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

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
Next revisionBoth sides next revision
util:sbbsecho [2020/03/10 21:54] – [Configure] be more helpful digital manutil:sbbsecho [2020/03/10 22:13] – [Instances] missing word digital man
Line 181: Line 181:
  
 === 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 ''Non-secure Inbound Directory'' setting in EchoCfg/''[[config:sbbsecho.ini]]'' and removed from future versions of [[SCFG]].+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 ''Non-secure Inbound Directory'' setting in EchoCfg/''[[config:sbbsecho.ini]]'' and removed from future versions of [[SCFG]]).
  
  
Line 957: Line 957:
 ==== Instances ==== ==== Instances ====
  
-SBBSecho is designed to run only one instance at a time. A mutual-exclusion file (''[[dir:ctrl]]/sbbsecho.bsy'') is used to insure that multiple instances of SBBSecho are not allowed to execute concurrently. If SBBSecho crashes or is externally-killed without being able clean up after itself, it's possible this mutex file will be left behind and prevent SBBSecho from running normally for quite some time (depending on the configuration value of ''BSY Mutex File Timeout'').+SBBSecho is designed to run only one instance at a time. A mutual-exclusion file (''[[dir:ctrl]]/sbbsecho.bsy'') is used to insure that multiple instances of SBBSecho are not allowed to execute concurrently. If SBBSecho crashes or is externally-killed without being able to clean up after itself, it's possible this mutex file will be left behind and prevent SBBSecho from running normally for quite some time (depending on the configuration value of ''BSY Mutex File Timeout'').
  
 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:

Trace: