Synchronet v3.20d-Win32 (install) has been released (Mar-2025).

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
faq:misc [2023/02/16 19:01] – [New User Feedback] Mention the new location of the new user feedback requirement setting in SCFG digital manfaq:misc [2025/05/19 12:42] (current) – [No Guest] Server->Terminal Server->Login Requirements is now the preferred method to disable guest logins to the BBS digital man
Line 14: Line 14:
   * [[#ftn_msgid|Why do my FidoNet MSGID's look different than someone else's]]?   * [[#ftn_msgid|Why do my FidoNet MSGID's look different than someone else's]]?
   * [[#old_baja|Why won't an old Baja source file compile without errors]]?   * [[#old_baja|Why won't an old Baja source file compile without errors]]?
 +  * [[#sizeof_scfg|Why do I get this error about cfg->size != sizeof(scfg_t)]]?
   * [[#spell|How do I spell "Synchronet"]]?   * [[#spell|How do I spell "Synchronet"]]?
   * [[#abbreviate|How do I abbreviate "Synchronet"]]?   * [[#abbreviate|How do I abbreviate "Synchronet"]]?
   * [[#syncterm|How do I report a problem or request a feature for SyncTERM]]?   * [[#syncterm|How do I report a problem or request a feature for SyncTERM]]?
 +  * [[#k:line|What is an AKILL on IRC and why was I K:Lined]]?
  
 ===== Deleted Msgs ===== ===== Deleted Msgs =====
Line 40: Line 42:
  
 :!: **Answer:**\\ :!: **Answer:**\\
-Many of the "New User" Questions can be disabled by setting various options in [[util:SCFG]]->System->New User Values->Question Toggles to "No":+Many of the "New User" Questions can be disabled by setting various options in [[util:SCFG]]->System->New User Prompts... to "No":
 <code> <code>
 ╔══════════════════════════════════╗ ╔══════════════════════════════════╗
Line 113: Line 115:
  
 :!: **Answer:**\\ :!: **Answer:**\\
-You don't have to have a Guest (G-[[access:restrictions|restricted]] user) account. If you don't create a Guest account to begin with, you won't have one. If you created a Guest account and you don't want it, then simply deleting the user account from the user base will work. However, without a Guest account, anonymous FTP access will not be available and some web UI elements may not function as is normally expected. To keep the Guest account but disallow logins to the Terminal Server (the traditional BBS user experience), set [[util:SCFG]]->Nodes->Node X->Logon Requirements->Requirement String to:+You don't have to have a Guest (G-[[access:restrictions|restricted]] user) account. If you don't create a Guest account to begin with, you won't have one. If you created a Guest account and you don't want it, then simply deleting the user account from the user base will work. However, without a Guest account, anonymous FTP access will not be available and some web UI elements may not function as is normally expected. To keep the Guest account but disallow logins to the Terminal Server (the traditional BBS user experience), set [[util:SCFG]]->Servers->Terminal Server->Login Requirements (or [[util:SCFG]]->Nodes->Node X->Login Requirements) ... Requirement String to:
   NOT GUEST   NOT GUEST
  
Line 168: Line 170:
 If the source (old) and target (new) computers are both running a Unix-like operating system (e.g. Linux), be sure to rebuild *all* the native executable binaries (''e.g. libsbbs.so''), including 3rd party libraries (e.g. ''libcl.a'') on the new/target computer before trying to execute them. Failure to do so could result in "invalid opcode" errors. If the source (old) and target (new) computers are both running a Unix-like operating system (e.g. Linux), be sure to rebuild *all* the native executable binaries (''e.g. libsbbs.so''), including 3rd party libraries (e.g. ''libcl.a'') on the new/target computer before trying to execute them. Failure to do so could result in "invalid opcode" errors.
  
-Configuration changes made via the ''[[:util:SCFG]]'' utility are stored in the ''*.cnf'' files in your ''[[dir:ctrl]]'' directory.+Configuration changes made via the ''[[:util:SCFG]]'' utility are stored in the ''*.ini'' (previously, ''*.cnf'') files in your ''[[dir:ctrl]]'' directory.
  
 If you wish to **only** migrate configuration and data files (e.g. over an new installation of Synchronet), copy (recursively) the following Synchronet sub-directories to the new computer: If you wish to **only** migrate configuration and data files (e.g. over an new installation of Synchronet), copy (recursively) the following Synchronet sub-directories to the new computer:
   * ''[[dir:data]]''   * ''[[dir:data]]''
   * ''[[dir:ctrl]]''   * ''[[dir:ctrl]]''
-  * ''[[dir:node]]1''+  * ''[[dir:node]]*''
  
-If you customized any of your filter (''*.can'') or menu (e.g. ''*.asc'') files, you'll also want copy (recursively) the following directory:+If you customized any of your filter (''*.can'') or menu (e.g. ''*.asc'', ''*.msg'') files, you'll also want copy (recursively) the following directory:
   * ''[[dir:text]]''   * ''[[dir:text]]''
  
Line 185: Line 187:
   * ''[[dir:xtrn]]''   * ''[[dir:xtrn]]''
    
-**Note:** Sysop-installed (e.g. not from [[:dev:CVS]]) or modified modules should not normally be stored in your ''[[dir:exec]]'' directory, but if they were, then you'll want to copy those over as well.+**Note:** Sysop-installed (e.g. not from [[:dev:Git]]) or modified modules should not normally be stored in your ''[[dir:exec]]'' directory, but if they were, then you'll want to copy those over as well.
  
  
Line 282: Line 284:
      
 **Note:** To see a complete list of changes in Baja v2, see {{http://synchro.net/docs/baja2new.txt}}. **Note:** To see a complete list of changes in Baja v2, see {{http://synchro.net/docs/baja2new.txt}}.
 +
 +===== sizeof scfg =====
 +:?: **Question:**\\
 +Why do I get the following error when running a Synchronet program: ''cfg->size(x) != sizeof(scfg_t) (y)''?
 +
 +:!: **Answer:**\\
 +The program you're trying to run (e.g. ''sbbs'', ''sbbsctrl'', ''jsexec'') was built from a different version/revision of the Synchronet code base than the Synchronet library: ''sbbs.dll'' (on Windows) or ''libsbbs.so'' (on UNIX) it's loading from disk.
 +
 +Look for extra/additional Synchronet library files and executables on your file system (e.g. in your Synchronet ''[[dir:exec]]'' directory?) and remove or rebuild them.
  
 ===== Spell ===== ===== Spell =====
Line 308: Line 319:
 :!: **Answer:**\\ :!: **Answer:**\\
 On sourceforge.net, [[https://sourceforge.net/p/syncterm/feature-requests/|feature requests]] and [[https://sourceforge.net/p/syncterm/tickets/|bug reports]]. On sourceforge.net, [[https://sourceforge.net/p/syncterm/feature-requests/|feature requests]] and [[https://sourceforge.net/p/syncterm/tickets/|bug reports]].
 +
 +===== K:Line =====
 +:?: ** Question:**\\
 +What is an AKILL on IRC and why was I K:Lined?
 +
 +:!: **Answer:**\\
 +AKILL is a feature of IRC services that will distribute a K:Line to all the other servers in the network. A K:Line is a server ban for your specific hostname or IP address. This means if you are AKILLed then you're banned from every other server. This is done to protect the network from spambots, flooders, and continually disruptive elements. AKILLs are done either manually by a Services Operator, or automatically by use of various methods employed by the IRCops.
 +
 +If you believe you have been accidentally or unfairly AKILLed from the Synchronet IRC network, contact sysop@endofthelinebbs.com with your IRC nickname, ip address, hostname (if you have one), date and time, including timezone, and any other relevant details. 
  
 ===== See Also ===== ===== See Also =====

Trace: