Skip to content
Snippets Groups Projects
  1. Aug 15, 2018
    • rswindell's avatar
      This is just something I noticed while looking into the change for the · 24f68cc2
      rswindell authored
      previous commit: don't clear the line counter or call pause() - which will
      do nothing - if the console abort flag is set.
      24f68cc2
    • rswindell's avatar
      This is a bit of a hack for Nelgin, who noticed that novice menu mode · f61e7d93
      rswindell authored
      would not always auto-redisplay menu files when the user hits 'Q' (or 'N'
      or Ctrl-C) at auto-pause prompts:
      
      When displaying a "message" (e.g. file), if the console abort flag is set
      before a single line has been displayed, clear the abort flag. This most
      likely means a pause (hit a key) prompt was automatically displayed due to
      a clear screen code in the message/file and the user hit 'Q' or 'N' or
      Ctrl-C at the prompt. In this special case, don't treat that as an
      "abort message" command and keep displaying the message/file.
      
      Once one or more lines in the message/file have been displayed, then the
      behavior is the same as before: a console abort (even as a result of an
      auto-pause prompt key) will stop the display of the current message/file.
      f61e7d93
    • rswindell's avatar
      Fix problem reported by Nelgin: · 833246cf
      rswindell authored
      In External programs after running Sycnrhonet BBS List you get
      "Returning to <BBS> - hit a key". If you presss Q you get a blank external
      menu menu rather than the full menu.
      The main problem was the line counter, so clearing after returning from
      executing an external program (unless the forced pause thing is on).
      833246cf
    • rswindell's avatar
      Count blank requests as "bogus commands". · 46985b5b
      rswindell authored
      Throttle bogus command sending clients (one second per bogus command, accumulating).
      46985b5b
  2. Aug 14, 2018
    • echicken's avatar
      seem like maybe addrs should be a array · a7c17211
      echicken authored
      a7c17211
    • rswindell's avatar
      Fix-up js_recvline() based on infinite error/log message report from Nelgin: · 13d22506
      rswindell authored
       term 0087 TLS ERROR 'Unexpected <Unknown type> (24) packet, expected application_data (23)' (-1) popping data
       message repeated 492 times: [ term 0087 TLS ERROR 'Unexpected <Unknown type> (24) packet, expected application_data (23)' (-1) popping data]
      
      When using TLS with a JS Socket object, if there was any kind of data error,
      the recvline() method would return a blank string rather than null/undefined.
      nntpservice.js just loops when it receives a blank string, so this caused an
      infinite loop (with disk-filling error log messages).
      
      First change: if no data has been received (i == 0) and there's any kind of
      receive error or timeout or disconnection, just return null. And not undefined,
      but null (!) like in v3.15 (before the great JS engine update of 2000-mumble).
      Also, there appeared to be a JS_RESUMEREQUEST call missing in the TLS error
      return case - so that's another bug fixed.
      Commented on the magic return values for js_sock_read_check()
      and js_socket_recv().
      Simplified js_sock_read_check() return value a tad: let the caller decide if
      they want to do something special based on the value of 'i'.
      Added some comments to make this code more readable.
      
      We are now no longer treating the different error return values (0 and -1) from
      js_socket_recv() special in this function, but we dont' treat them special in
      any of the other calls in this file/object either, so that seems to be the
      norm.
      13d22506
    • rswindell's avatar
      The timeout parameter to js_socket_recv() is in seconds. I don't think · 8de4c1b7
      rswindell authored
      Deuce really wanted to pass 1000 as a value here (use 1 instead). I don't
      know if this was an observable problem or not, but it certainly *looks*
      like a bug.
      8de4c1b7
  3. Aug 09, 2018
  4. Aug 08, 2018
  5. Aug 07, 2018
    • rswindell's avatar
      Incremented version to 3.06 · 9eaf77be
      rswindell authored
      Added version for Bill McGarrity: for each linked-node, a preferred
      local address (AKA) can be specified to be used as the source address
      when creating packets destined for that linked-node. If no local address
      is specified, the previous (best match) logic is used: find an AKA that
      has the same zone and net as the destination address, if none found, use
      the first address with the same zone.
      9eaf77be
    • rswindell's avatar
      If the user number is 0, don't open the user file (user.dat) - the read · ed94a0d6
      rswindell authored
      of the user record is going to fail anyway. *this* explains a lot of
      instances of the user.dat file being open concurrently, at least one per
      active thread with a JS context.
      ed94a0d6
    • rswindell's avatar
      js_CreateUserObject(): if passed an internal user_t representation, the · 7cee046f
      rswindell authored
      user data is thusly cached - set the 'cached' property member to TRUE. This
      prevents an unnecessary re-read of the user file and the leaving the user file
      (user.dat) open, at least for JS contexts that contain a "user" object. I don't
      think this explains the "too many open files" errors, but it explains at least
      *some* number of the user.dat open file descriptors.
      7cee046f
  6. Aug 03, 2018
  7. Aug 01, 2018
  8. Jul 31, 2018
  9. Jul 30, 2018
  10. Jul 29, 2018
Loading