• User List / Logon List

    From Eastside75@1:103/705 to All on Sat Aug 16 08:09:48 2025
    When viewing the (U)ser list and selecting todays logons, it shows every logon from day 1 and when chosing Yesterdays logons, there were no logons?

    Any ideas on this one? Default command shell.

    ---
    þ Synchronet þ Thunder-Line BBS - thunder.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Eastside75 on Sat Aug 16 13:22:42 2025
    Re: User List / Logon List
    By: Eastside75 to All on Sat Aug 16 2025 08:09 am

    When viewing the (U)ser list and selecting todays logons, it shows every logon from day 1 and when chosing Yesterdays logons, there were no logons?

    Any ideas on this one? Default command shell.

    In the stock/default configuration, SCFG->External Progarms->Fixed Events->Daily Event is set to:

    Enabled Yes
    Native Executable No
    Use Shell or New Context No
    Command Line ?logonlist -m

    That "logonlist -m" command maintains the logon list files (data/logon[.*].jsonl). It needs to run daily.
    --
    digital man (rob)

    Synchronet "Real Fact" #57:
    Synchronet introduced Telnet, FTP, SMTP and POP3 support w/v3.00a-Win32 in 2000 Norco, CA WX: 75.0øF, 64.0% humidity, 5 mph W wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Eastside75 on Sat Aug 16 13:25:47 2025
    Re: User List / Logon List
    By: Digital Man to Eastside75 on Sat Aug 16 2025 01:22 pm

    Re: User List / Logon List
    By: Eastside75 to All on Sat Aug 16 2025 08:09 am

    When viewing the (U)ser list and selecting todays logons, it shows every logon from day 1 and when chosing Yesterdays logons, there were no logons?

    Any ideas on this one? Default command shell.

    In the stock/default configuration, SCFG->External Progarms->Fixed Events->Daily Event is set to:

    Enabled Yes
    Native Executable No
    Use Shell or New Context No
    Command Line ?logonlist -m

    That "logonlist -m" command maintains the logon list files (data/logon[.*].jsonl). It needs to run daily.

    Also, this event is automatically installed when running 'jsexec update.js' (part of the update instructions) are manually: https://wiki.synchro.net/module:logonlist#install
    --
    digital man (rob)

    Synchronet "Real Fact" #54:
    The Synchronet source code consists of over 500,000 lines of C and C++
    Norco, CA WX: 75.0øF, 64.0% humidity, 5 mph W wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Eastside75@1:103/705 to Digital Man on Sat Aug 16 16:47:21 2025
    Re: User List / Logon List
    By: Digital Man to Eastside75 on Sat Aug 16 2025 01:25 pm

    Events->> Daily Event is set to:

    Enabled Yes
    Native Executable No
    Use Shell or New Context No
    Command Line ?logonlist -m

    This already appears as formated above.

    Also, this event is automatically installed when running 'jsexec update.js' (part of the update instructions) are manually: https://wiki.synchro.net/module:logonlist#install

    This was a fresh 3.2 install and not an upgrade.

    ---
    þ Synchronet þ Thunder-Line BBS - thunder.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Eastside75 on Sat Aug 16 16:04:45 2025
    Re: User List / Logon List
    By: Eastside75 to Digital Man on Sat Aug 16 2025 04:47 pm

    Re: User List / Logon List
    By: Digital Man to Eastside75 on Sat Aug 16 2025 01:25 pm

    Events->> Daily Event is set to:

    Enabled Yes
    Native Executable No
    Use Shell or New Context No
    Command Line ?logonlist -m

    This already appears as formated above.

    Also, this event is automatically installed when running 'jsexec update.js' (part of the update instructions) are manually: https://wiki.synchro.net/module:logonlist#install

    This was a fresh 3.2 install and not an upgrade.

    What logon*.jsonl files do you have in your data directory?

    What is the "Date" value in your ctrl/dsts.ini file?
    --
    digital man (rob)

    Sling Blade quote #26:
    Karl: kaiser blade, ax handle with long blade on it shaped kinda like a banana. Norco, CA WX: 80.3øF, 55.0% humidity, 9 mph W wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Eastside75@1:103/705 to Digital Man on Sun Aug 17 07:02:30 2025
    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"?

    ---
    þ Synchronet þ Thunder-Line BBS - thunder.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Eastside75 on Sun Aug 17 12:33:54 2025
    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)

Novedades:

Servidor de Quake 3 Arena Online! - Conectate a ferchobbs.ddns.net, puerto 27960 y vence con tu equipo!