1. 09 Jun, 2017 2 commits
  2. 07 Jun, 2017 2 commits
    • rswindell's avatar
      When importing dirs.raw/Directory Listings into a library: · a3554a8f
      rswindell authored
      1. Randomize the last 3 characters of the internal code to generate a unique
         internal code.
      2. Attempt to skip sub-directory names when generating long/short names from
         imported path, if no sub-dirs are in the path, then just right-justify the
         truncated path - trying to generate meaninful long/short names from long
      3. Do not allow duplicate paths to be imported into the same library.
      4. Skip (do not import) directory entries that are > 63 chars in length.
      5. Stop importing if/when total dirs >= MAX_DIRS (65534).
    • rswindell's avatar
      Add #defines for MAX_SUBS, MAX_DIRS, and MAX_XTRNS (65534). · 24f149d7
      rswindell authored
      If anybody actually hit these limits I'd be impressed, but it's not impossible.
      65535 (-1 as an int16_t) is a special value used to indicate an "invalid" item.
  3. 05 Jun, 2017 1 commit
    • rswindell's avatar
      Improvements to dirs.raw/directory listing import into file library: · c7d39477
      rswindell authored
      1. added option to import empty sub-directories (previously empty subdirs were
          always ignored).
      2. attempt to generate a unique internal code when the auto-generated internal
          code (based on the characters in path) is not unique.
      3. display "Scannnig Directories..." popup since this can take a while
          (especially on network drives and especially recurisvely).
      Note: if you're importing lots of deeply nested subdirs, it's likely that a
      unique internal code can't be generated (from the path) for all subdirs.
      A randomly generated internal code might be an option if this is really
      a problem for any sysops.
      Also updated the brace style of this .c file, finally.
  4. 04 Jun, 2017 2 commits
    • rswindell's avatar
      Replace "<unknown>" as the "Unknown User" string with "<unknown user>" · c635c3ac
      rswindell authored
      globally (using a new macro in sbbbsdefs.h: STR_UNKNOWN_USER). "<unknown>"
      in some contexts was too vague (e.g. the 'c' command output from the sbbs
    • rswindell's avatar
      1. Fixed "always syslog" mode Used to force log output to syslog even when · 7ca2cf57
      rswindell authored
         not daemonized: log output would be repeated (once with a timestamp in
         the log string, once without). Now direct calls to lputs/lprintf from
         sbbscon.c won't go to syslog (in this mode), but I think that's okay.
      2. Change the prompt when terminating the servers: replace the ?=help and
         colon implying you can enter commands with just "Termianting..." since
         you can't actually type commands while a terminate is in progress.
      3. Output the inactivity timeout values when waiting for servers to
         terminate (e.g. because they'res till in use).
      4. Report IP addresses in square-brackes in the client ('c' command) output
         to differentiate from hostnames.
  5. 03 Jun, 2017 3 commits
  6. 02 Jun, 2017 1 commit
  7. 22 May, 2017 2 commits
  8. 10 May, 2017 1 commit
  9. 26 Apr, 2017 1 commit
  10. 23 Apr, 2017 1 commit
    • nightfox's avatar
      Version 1.17 beta 36: Updated the newscan loop to wait 10ms at the end of the... · e4f9fbb5
      nightfox authored
      Version 1.17 beta 36: Updated the newscan loop to wait 10ms at the end of the loop to avoid causing CPU usage to go high while the newscan loop is running (CPU usage was getting to 99% on my BBS system).  With the 10ms wait, CPU usage went down to 65-70% on my BBS system, so it seems this should help keep the CPU workload from getting so high.
  11. 11 Apr, 2017 1 commit
    • rswindell's avatar
      Another change for Bill: · 79e4c4b7
      rswindell authored
      Added (back) the '-d' command-line option to disable the deletion of processed
      (e.g. imported) inbound netmail messages.
      - This option has no effect if DeleteNetmail is set to "false" in sbbsecho.ini.
      - This option *only* disables deletion of incoming netmail (no effect on
        outbound netmail deletion)
      - In SBBSecho v2, the '-d' option disabled all netmail deletion, even though
        the help output only mentioned "netmail after import" (it was wrong).
  12. 06 Apr, 2017 1 commit
  13. 04 Apr, 2017 1 commit
  14. 22 Mar, 2017 1 commit
  15. 13 Mar, 2017 1 commit
  16. 07 Mar, 2017 1 commit
  17. 06 Mar, 2017 4 commits
  18. 03 Mar, 2017 1 commit
  19. 01 Mar, 2017 4 commits
    • rswindell's avatar
      +1 for NULL terminator. · 097a0825
      rswindell authored
    • rswindell's avatar
      Fix GCC warnings: · e95e0dae
      rswindell authored
      sbbsecho.h:186:7: warning: array æpktTypeStringListÆ assumed to have one element
      Warning: size of symbol `pktTypeStringList' changed from 8 in .../rechocfg.o
    • rswindell's avatar
      Packet Type-2e (FSC-39.4) support: · aace645d
      rswindell authored
      For packet creation, the only difference (from Type-2+) is with packets created
      from point nodes: the origNet field won't be set to 0xffff (as is the case with
      FSC-48, Type-2+ packets). The auxNet field is now always set to the originating
      net (ala Squish) when configured for Type-2+ packet generation.
      When importing Type-2e (FSC-39) packets, the detected/logged packet type may be
      reported as "2e" for valid "2+" packets. This is normal and expected when the
      originating node is not a point and the auxNet field is 0.
      The second set of orig/dest zone fields in a type 2e/2+ pkt header will
      now be used when importing if the old/QM orig/dest zone fields are 0.
      Also, the originating point field may now be imported even if the auxNet field
      is not used (origNet != 0xffff).
      New umask sbbsecho.ini configuration option (global), maybe used to over-ride
      the default *nix file creation mode mask (077), similar to sbbs.ini.
    • rswindell's avatar
      Changes in comments only: · dbaa70bc
      rswindell authored
      Use more formal terminology (e.g. "Type-2", not "type 2.0").
  20. 27 Feb, 2017 2 commits
  21. 24 Feb, 2017 1 commit
    • rswindell's avatar
      2 Area-fix changes with regards to "pass-through areas": · 62f7e8ed
      rswindell authored
      - %RESCAN returns a different failure result if the requested echo is a
      pass-through area (cannot be rescanned)
      - %UNLINKED will return only the unlinked echoes even when an "additional
      echolist" is utliized and the linked areas are all pass-through (for Bill).
  22. 21 Feb, 2017 2 commits
    • rswindell's avatar
      Fix potential crash (stack corruption) in qwk_route() reported by Hemo: · 2ff51deb
      rswindell authored
      If what appears to be a QWKnet addressed was passed, but the QWK-ID portion was
      exactly 9 characters, a 1-byte stack corruption would occur as the 10-char
      local variable (node) could be written with 11 chars (9-char QWK-ID, colon,
      null). The reported issue happend when attempting to send netmail to
      "hemo@ujointbbs" which is neither a valid Internet email address or a valid
      QWKnet address.
    • nightfox's avatar
      Version 0.16 beta: Added a main menu option to display poll stats - Lists the... · f9a83a63
      nightfox authored
      Version 0.16 beta: Added a main menu option to display poll stats - Lists the polls by highest number of votes (highest first), and for each one, lists the answer(s) with the highest number of votes (highest first).
  23. 20 Feb, 2017 1 commit
  24. 12 Feb, 2017 1 commit
  25. 10 Feb, 2017 1 commit
    • rswindell's avatar
      Added IPv4 CIDR notation support to all filter (*.can) files via the functions: · 26524908
      rswindell authored
      findstr() and findstr_in_list().
      This means that rather than listing an IP address range using the traditional
      wildcard characters (e.g. "192.168.1.*"), you could specify a subnet range
      using CIDR notation (e.g. "").
      The '!' prefix is supported for CIDR match lines (for negated match results),
      but no other wildcard/match characters are (e.g. '^', '~', or '*').
      You can mix and match traditional match lines and CIDR match lines in the same
      filter file.
      IPv6 CIDR notation is not yet supported.
  26. 09 Feb, 2017 1 commit