TZUTC: 1100   
   MSGID: 50206.dove-syncdisc@12:1/2 2bc8626c   
   REPLY: 53256.sync@1:103/705 2bc86178   
   PID: Synchronet 3.20a-Linux master/7b932f63e Dec  9 2023 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/bbf9d5eac Dec 14 2024 GCC 12.2.0   
   COLS: 80   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: JS Object save_msg()   
     By: Digital Man to deon on Tue Dec 17 2024 09:19 pm   
      
   Howdy,   
      
    >  > OK, it is UTC in there.   
    >   
    > Is that intentional?   
      
   No. This is a vanilla, mostly unconfigured, install of Sync (running on my   
   laptop that I use to build my ansitex shell).   
      
    > Synchronet doesn't figure it out, it just uses the timezone you have   
    > configured in SCFG->System.   
      
   It figures out the "current time" (from the OS?) to store in the   
   when_imported_time and when_written_time fields though right? I would have   
   thought it would be easy to get the timezone from the OS, to populate the   
   *_zone fields?   
      
    > timezone don't agree, the Terminal Server logs a warning during startup:   
    > "Configured time zone (x, 0xYYYY, offset: z) does not match system-local   
    > time zone offset: n"   
    >   
    > Are you getting this warning log message?   
      
   Dont know, hadnt looked. With the other stuff the gets spawed out when   
   starting sync, it doesnt stand out. (I just restarted, and yes its there, but   
   it doesnt look like a "warning" against all the other informational messages.)   
      
    > You have a mismatch in your configuration. If that's unintentional, then I   
    > guess I could make that warning log message an error instead, to hopefully   
    > insure that sysops are aware of it in the future. If it's intentional, then   
    > I guess I would want to know why and then figure out how to support such a   
    > configuration with fewer surprises.   
      
   Can you always get the timezone from the OS? Why have a configured timezone at   
   all? If I want to display everything in a timezone, then sure, that makes   
   sense (eg: my host is in a VM in country "X", but I am in country "Y"), but to   
   work out and manipulate dates/times I would have thought you could do that all   
   based on what the OS returns?   
      
    > Are you messing with your system's timezone configuration or TZ environment   
    > variable?   
      
   No. Cant imagine a timezone configuration or TZ variable that would still   
   return +11:00/AEDT but be 12 hrs ago (hence why I used the OS's date command   
   in the example output to show what the OS's time was).   
      
      
   ...ëîåï   
      
   ---   
    þ Synchronet þ AnsiTEX bringing back videotex but with ANSI   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 550 700 705 240/1120 5832 266/512 280/464   
   SEEN-BY: 280/5003 5006 282/1038 291/111 292/8125 301/1 310/31 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426