1. 24 Mar, 2022 2 commits
    • Rob Swindell's avatar
      Fix newly-introduced GCC warnings · 9405250f
      Rob Swindell authored
      9405250f
    • Rob Swindell's avatar
      Support user credits and transfer stats > 4GB in total · 1cac2c8a
      Rob Swindell authored
      Credits and daily free credits are accurate to the byte up to (a maximum) of 18446744073709551615 (that's 18 Exbibytes - 1).
      
      User's upload and download byte stats are now similarly extended in maximum range, but the accuracy is only "to the byte" for values less than 10,000,000,000. Beyond that value, the accuracy declines, but is generally pretty damn accurate (to 4 decimal places beyond the nearest multiple of a power of 1024), so I don't expect that to be an issue. This method of storing upload/download byte stats allowed me to use the same 10-character user record fields in the user.dat file.
      
      As a side-effect of this enhancements:
      * User and file credit values are now expressed in multiples of powers of 1024 (e.g. 4.0G rather than 4,294,967,296).
      * Free credits per day per security level has now been extended from 32 to 64-bits (to accommodate values >= 4GB).
      * adjustuserrec() now longer takes the record length since we can easily determine that automatically and don't need more "sources of truth" that can be out-of-sync (e.g. the U_CDT field length going from 10 to 20 chars with this change).
      * setting the stage for locale-dependent thousands-separators (e.g. space instead of comma) - currently still hard-coded to comma
      * more/better support for files > 4GB in size (e.g. in the batch download queue)
      * user_t ulong fields changed to either uint32_t or uint64_t - I didn't realize how many long/ulong's remained in the code (which are sometmies 32-bit, sometimes 64-bit) - ugh
      * Steve's ultoac() function renamed to u32toac() and created a C++ wrapper that still uses the old name, for homage
      1cac2c8a
  2. 28 Feb, 2022 1 commit
  3. 25 Feb, 2022 1 commit
  4. 24 Feb, 2022 1 commit
  5. 04 Apr, 2021 2 commits
  6. 14 Feb, 2021 1 commit
  7. 18 Jan, 2021 1 commit
  8. 25 Oct, 2020 2 commits
  9. 03 Oct, 2020 1 commit
  10. 25 Sep, 2020 1 commit
    • Rob Swindell's avatar
      Fix crash in createdefaults() when SBBSCTRL environment variable not set · 20ffe45f
      Rob Swindell authored
      Don't re-read the configuration - we already have it in memory, just pass it
      by reference to createdefaults(), so we don't need the SBBSCTRL environment
      variable (again). As reported by Michael Long via alt.bbs.synchronet.
      
      Also addressed the truncation of the new user chat handle as reported by GCC.
      20ffe45f
  11. 17 Aug, 2020 1 commit
  12. 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).
      54431b31
    • Rob Swindell's avatar
      Commit with CVS Keywords expanded. · dfa1a0a4
      Rob Swindell authored
      dfa1a0a4
  13. 12 Apr, 2020 1 commit
  14. 02 Apr, 2020 2 commits
  15. 09 Jan, 2020 1 commit
  16. 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).
      b236be71
  17. 25 Sep, 2019 1 commit
  18. 24 Aug, 2019 1 commit
  19. 29 Jun, 2019 2 commits
  20. 01 Jan, 2019 1 commit
  21. 25 Oct, 2018 1 commit
  22. 24 Jul, 2018 1 commit
  23. 23 Feb, 2018 1 commit
  24. 13 Dec, 2017 2 commits
  25. 13 Nov, 2017 1 commit
  26. 28 Nov, 2016 1 commit
  27. 27 Aug, 2015 3 commits
  28. 14 Feb, 2014 1 commit
  29. 13 Feb, 2014 2 commits
  30. 15 Jun, 2012 1 commit