Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dailybuild_linux-x64
  • dailybuild_win32
  • 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
  • new_user_dat
  • 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

sbbs

  • Clone with SSH
  • Clone with HTTPS
  • Rob Swindell (on Debian Linux)'s avatar
    Rob Swindell authored
    As Deon pointed out in DOVE-Net / Synchronet Discussion, having a local time
    zone configured with a different UTC offset than your system time zone can
    produce strange/unexpected results (e.g. displayed age of messages). Since
    it's possible that not all sysops will complete the configuration wizard or
    actually set their timezone to the correct value (and ignore the startup
    warning message), we now make the default Local Time Zone to be
    "automatic" - query the OS every time the local time zone is needed/used.
    
    This has the downside of only storing (e.g. in message headers) the UTC
    offset of the current time zone (not the time zone abbreviation/name as
    encoded by SMB). I considered making an option to dynamically figure out
    the actual time zone (not just the UTC offset) and while I think that's
    doable, Deon just wanted his UTC offset (e.g. UTC+11:00) and not his
    time zone name (e.g. AEDT) stored in message headers, so this setting
    would be the behavior he expected/wanted.
    
    I'm using the sentinel time zone value of -1 for this new behavior.
    
    Existing configurations (behavior of existing systems) aren't changed.
    5434b904
    History
    Name Last commit Last update