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

  1. 14 Nov, 2020 2 commits
    • Rob Swindell's avatar
      Restore console to "cooked" mode before daemonizing(). · 8cdd0422
      Rob Swindell authored
      Previously, the console would be left in "raw" mode after invoking
      'jsexec -d <module>'.
    • Rob Swindell's avatar
      More control over output streams · 74b4a948
      Rob Swindell authored
      Added options -A[filename] and -S[filename] to allow more control over which output streams go where (for mlong and his troubles with running ircd via systemd).
      -A controls "all messages" either sending all to stdout or the specified filename. This override the automatic suppression of the console output stream when run without a controlling TTY.
      -S controls "status message" (includes non-error level log messages), either sending the status messages to stdout or the specified filename. This also overrides the automatic suppression of the console output stream when run without a controlling TTY.
  2. 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.
  3. 17 Aug, 2020 1 commit
  4. 16 Aug, 2020 2 commits
    • Rob Swindell's avatar
      Fix issue with jsexec being used for CGI scripts · 54431b31
      Rob Swindell authored
      If jsexec is used for a CGI script and the SBBSCTRL env var was not
      set, a warning would be printed (to stderr), even if the -c option
      was used to specify the path to the ctrl dir.
      get_ctrl_dir() now accepts a boolean argument to specify whether to
      print a warning when the default value ("/sbbs/ctrl") is used.
      Pass FALSE for jsexec, TRUE for other callers (currently).
    • Rob Swindell's avatar
      Commit with CVS Keywords expanded. · dfa1a0a4
      Rob Swindell authored
  5. 05 May, 2020 1 commit
  6. 04 May, 2020 1 commit
    • rswindell's avatar
      Move expected location of jsexec.ini from exec directory to ctrl directory: · 703289d1
      rswindell authored
      - argv[0] does not always contain the full path to the executable, so that is
        not a good way to locate the exec directory.
      - since we already need to know the ctrl dir and that is the normal place to
        put config files, that's where it shall be.
      - jsdoor builds don't get a .ini file - I don't think they need it (?)
  7. 12 Apr, 2020 2 commits
  8. 08 Apr, 2020 1 commit
    • rswindell's avatar
      Added support for exec/jsexec.ini file which can over-ride default values · 77a8d33c
      rswindell authored
      globally and per-module. Command-line options still take precedence.
      For jsdoor builds, jsdoor.ini is supported in whatever directory jsdoor is run
      Changed the default log level from Debug to Informational.
      (If you need the old default, set LogLevel=debug in your ctrl/jsexec.ini file).
  9. 03 Jan, 2020 1 commit
    • rswindell's avatar
      Add/use a new get_ctrl_dir() function to query the SBBSCTRL env var and if · b236be71
      rswindell authored
      not set (or blank), use the default ("/sbbs/ctrl") and print a warning to
      stderr. This resolves a FAQ for sysops that struggle with setting the SBBSCTRL
      env var, but do have sbbs install in /sbbs or a symlink from /sbbs to where
      sbbs is actually installed.
      Note: this function is different than the one previously defined in getctrl.c
      but never used. If/when we ever really need to support PREFIX, then perhaps
      we'll use that one (which copies a string to a buffer).
  10. 02 Sep, 2019 1 commit
  11. 29 Aug, 2019 1 commit
    • deuce's avatar
      We do *not* want JSOPTION_VAROBJFIX set since it causes variables to be · a563651f
      deuce authored
      created in the global scope when when a scope is passed to load(), require()
      or js.exec().
      While having 'var x = 0;' and 'x = 0;' put x in different scopes is bad, we
      actually want them all in the passed scope, not the global scope... and that's
      not an option.
      It looks like js.exec() will actually need to set scope as the global object
      and add a second global object to the original scope.
  12. 27 Aug, 2019 2 commits
  13. 08 Aug, 2019 1 commit
  14. 06 Aug, 2019 1 commit
  15. 29 May, 2019 1 commit
  16. 20 Jan, 2019 2 commits
  17. 12 Dec, 2018 1 commit
  18. 22 Oct, 2018 1 commit
  19. 06 Apr, 2018 1 commit
  20. 09 Mar, 2018 1 commit
  21. 08 Mar, 2018 1 commit
  22. 20 Feb, 2018 2 commits
  23. 14 Feb, 2018 1 commit
  24. 12 Jan, 2018 1 commit
    • rswindell's avatar
      Added command-line option -C (capital 'C'): · 2596f5e5
      rswindell authored
      - This option instruts JSexec to *not* change the current working directory to
        the control (CTRL) directory
      - This is useful when using jsexec to deal with files and passing relative
        paths or wildcards on the command-line
      - Warning: scripts executed with this option may behave differently than the
        same script executed from SBBS where the current working directory is always
        the CTRL directory.
  25. 06 Jan, 2018 1 commit
  26. 30 Dec, 2017 3 commits
  27. 28 Nov, 2017 1 commit
  28. 27 Nov, 2017 1 commit
  29. 13 Nov, 2017 2 commits
  30. 15 Nov, 2016 1 commit
  31. 21 Jan, 2016 1 commit