Synchronet now requires the libarchive development package (e.g. libarchive-dev on Debian-based Linux distros, libarchive.org for more info) to build successfully.

  1. 22 Feb, 2021 2 commits
  2. 18 Feb, 2021 4 commits
  3. 16 Feb, 2021 2 commits
  4. 15 Feb, 2021 4 commits
  5. 14 Feb, 2021 1 commit
  6. 18 Jan, 2021 1 commit
    • Rob Swindell's avatar
      Safe string handling with config-load error messages · 99dbeb14
      Rob Swindell authored
      We were just trusting that the error strings would be shorter than 256 (usually), but since we're including paths and strerror() results, we really have no control over the length of the error strings. So enforce some healthy boundaries. This could explain the crashes that Divarin of Mutiny is seeing with SCFG on WinXP or maybe it was the truncsp(strerror()) stuff that was just removed as well. We'll see...
      99dbeb14
  7. 20 Dec, 2020 1 commit
  8. 13 Dec, 2020 4 commits
  9. 07 Dec, 2020 1 commit
  10. 29 Nov, 2020 4 commits
    • Rob Swindell's avatar
    • Rob Swindell's avatar
      Fallback to the "first node" configuration · 07bd3442
      Rob Swindell authored
      If a node's configuration can't be loaded (e.g. nodeX/node.cnf is missing), fall-back and load the "first node" (e.g. Node1) configuration. On recent *nix installs (since the migration to Git), the node2+/node.cnf files were not copied/created, so let's solve that soon-to-be-FAQ now.
      07bd3442
    • Rob Swindell's avatar
      Copy event last-run info from global config into node config · 827063bb
      Rob Swindell authored
      Fixes issue introduced in last commit to this file (the each-node-has-its-own-config-in-memory enhancement) that would prevent users from logging in because their time was reduced for an upcoming event that had already run. The change assumes the event thread is running (its the thing that reads the event last-run info from time.dab). Thanks to mlong for the report.
      827063bb
    • Rob Swindell's avatar
      Load/keep/refresh each node's configuration in memory. · 82d3ae6e
      Rob Swindell authored
      Previously, all nodes shared the same copy of the configuration in memory. This prevented any node from seeing an updated configuration until all nodes were offline or waiting for connection and could be recycled. Now, no recycling of the server is needed for a node to load a new config. A node in-use *still* cannot reload configuration until the user disconnects, but all you have to do is logon to another unused node and you (or that user) will get an updated configuration. Bots or server recycling problems will no longer prevent the sysop or user from getting a current configuration when connecting to any node.
      
      This is one of those instances of giving the sysop what he wants rather than what he asked for. I should've done this a long time ago, but the idea just occurred to me. You're welcome. :-)
      82d3ae6e
  11. 24 Nov, 2020 1 commit
    • Rob Swindell's avatar
      Stop pretending to configure the JavaScript Context stack · c0cd8686
      Rob Swindell authored
      The argument to JS_NewContext that we were allowing to be configured was not the contest stack size, but rather:
      "The size, in bytes, of each "stack chunk". This is a memory management tuning parameter which most users should not adjust. 8192 is a good default value." - per Mozilla.
      
      So we're just going to use the suggested default, hard-coded.
      c0cd8686
  12. 20 Nov, 2020 1 commit
  13. 19 Nov, 2020 1 commit
  14. 18 Nov, 2020 5 commits
  15. 17 Nov, 2020 1 commit
  16. 13 Nov, 2020 1 commit
    • Rob Swindell's avatar
      Add timestamp of node.log file to crash.log · bd78d5c5
      Rob Swindell authored
      When a preexisting node.log file is found, a terminal server crash is suspected. Include the timestamp of the node.log in the message appended to the system log (data/logs/*.log) to help identify the likely time of the crash.
      bd78d5c5
  17. 09 Nov, 2020 1 commit
  18. 06 Nov, 2020 1 commit
    • Rob Swindell's avatar
      Replace ctype.h function calls with new MSVC-safe XPDEV macros · 8a7b7308
      Rob Swindell authored
      I'm fed-up with MSVC assertions in ctype functions (e.g. isdigit, isprint, isspace, etc.) when called with out-of-range (e.g. negative) values.
      
      This problem only affects MSVC debug builds, but if you run them (like I do), these things are like little time bombs that can drive you crazy (knocking your board out of service).
      
      The new macros names are bit more descriptive as well.
      8a7b7308
  19. 05 Nov, 2020 1 commit
  20. 02 Nov, 2020 1 commit
    • Deon George's avatar
      Misc updates for sbbs/sbbs!11 · 9d66d732
      Deon George authored
      Use \n\r instead of \x0a\x0d.
      Change to memcpy instead of strcmp for v2 protocol validation
      Change read_socket error logging to WARNING, since the resulting error is diagnosed after the call.
      9d66d732
  21. 25 Oct, 2020 1 commit
  22. 23 Oct, 2020 1 commit