Skip to content
Snippets Groups Projects
Select Git revision
  • dd_area_choosers_split_string_infinite_loop_fix
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

userdat.h

Blame
    • Rob Swindell's avatar
      20cfdb18
      Split-up the opening and writing of msg pointer files, to help debug issue · 20cfdb18
      Rob Swindell authored
      Reported by Keyop (upon being auto-disconnected overnight):
      !ERROR 9 (Bad file descriptor) in data_ovl.cpp line 47 (putmsgptrs) writing
      "message pointers" access=0
      
      Unfortunately, the way putmsgptrs() was written, we couldn't tell if this was
      an open (data/user/*.subs file) issue or a writing issue.
      
      So create putmsgptrs_fp() and use that from sbbs_t::putmsgptrs(), so we can
      log a different error (with more accurate details) if it's a file-open failure
      versues a file-write failure.
      20cfdb18
      History
      Split-up the opening and writing of msg pointer files, to help debug issue
      Rob Swindell authored
      Reported by Keyop (upon being auto-disconnected overnight):
      !ERROR 9 (Bad file descriptor) in data_ovl.cpp line 47 (putmsgptrs) writing
      "message pointers" access=0
      
      Unfortunately, the way putmsgptrs() was written, we couldn't tell if this was
      an open (data/user/*.subs file) issue or a writing issue.
      
      So create putmsgptrs_fp() and use that from sbbs_t::putmsgptrs(), so we can
      log a different error (with more accurate details) if it's a file-open failure
      versues a file-write failure.