TZUTC: -0700   
   MSGID: 58518.sync_sys@1:103/705 2d084938   
   REPLY: 58515.sync_sys@1:103/705 2d08162a   
   PID: Synchronet 3.21a-Linux master/7a66d7f63 Aug 10 2025 GCC 12.2.0   
   TID: SBBSecho 3.29-Linux master/27cbebcb9 Aug 10 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: User List / Logon List   
     By: Eastside75 to Digital Man on Sun Aug 17 2025 07:02 am   
      
    >   Re: User List / Logon List   
    >   By: Digital Man to Eastside75 on Sat Aug 16 2025 04:04 pm   
    >   
    >  > What logon*.jsonl files do you have in your data directory?   
    >   
    >  > What is the "Date" value in your ctrl/dsts.ini file?   
    >  > --   
    >   
    > I simply have a logon.jsonl file, no number attribute   
    >   
    > The Date in dsts is "never"?   
      
   That's the underlying issue: your system isn't detecting a new day. The   
   current system date is compared against that dsts.ini "Date" value and if the   
   current date is different, resets stats (and runs the fixed events you have   
   configured in SCFG to run as specified date intervals). This is done for each   
   terminal sever logon (for non Q-restricted accounts) and periodically in the   
   terminal server "event thread".   
      
   As a result, you should see log messages like this (where the event thread   
   detected the new date):   
      
   BBS Events New Day - Prev: Fri Aug 15 2025 12:00 am   
   BBS Events New Day and Week - Prev: Sat Aug 16 2025 12:00 am   
      
   If the event thread isn't running or is busy running an event, but a new   
   terminal server logon occurs after a date change, you should see a similar log   
   message in the terminal server's log otuput.   
      
   The only things that would prevent this "rollover" from happening (and that   
   dsts.ini "Date" value being update to reflect the current date/time) are   
   issues reading the dsts.ini file (which should be logged accordingly) or   
   reading the current system date/time from the system clock.   
      
   So the next step is check what in the log output of your event thread (e.g.   
   data/events.log in most recent builds of sbbs), the terminal server, and your   
   data/error.log file for clues.   
   --    
                                               digital man (rob)   
      
   Rush quote #18:   
   Leave out condition, courageous convictions will drag the dream into existence   
   Norco, CA WX: 80.1øF, 57.0% humidity, 3 mph W wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.29-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757   
   SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 700 705 240/1120 5832   
   SEEN-BY: 263/1 266/512 280/464 5003 5006 291/111 292/8125 301/1 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 8912 5054/30   
   SEEN-BY: 5075/35   
   PATH: 103/705 280/464 460/58 229/426