• MSGMAINT

    From deon@VERT/ALTERANT to All on Sun Oct 25 11:10:00 2020
    Hey Rob,

    When I login to my SBBS on a Sunday, I get this message printed and in the log:

    Oct 25 15:05:37 p-1-1 synchronet: term Node 2 <deon> Node 2 Time reduced (to 13:54:23) due to upcoming event (msgmaint) on Mon Oct 26 2020 05:00 am

    The problem is - in SCFG, MSGMAINT is configured to run on Sunday, not Monday, and it appears it already ran:

    Oct 25 05:00:00 p-1-1 synchronet: evnt MSGMAINT Waiting for node 1 to run timed event: MSGMAINT
    Oct 25 05:00:00 p-1-1 synchronet: evnt MSGMAINT Waiting for all nodes to become inactive before running timed event
    Oct 25 05:00:01 p-1-1 synchronet: evnt MSGMAINT Running native timed event: MSGMAINT

    (This is a 2 week old build of SBBS).

    ...ëîåï

    ... A fanatic is one who can't change his mind and won't change the subject.

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
  • From Digital Man@VERT to deon on Sat Oct 24 18:19:00 2020
    Re: MSGMAINT
    By: deon to All on Sun Oct 25 2020 03:10 pm

    Hey Rob,

    When I login to my SBBS on a Sunday, I get this message printed and in the log:

    Oct 25 15:05:37 p-1-1 synchronet: term Node 2 <deon> Node 2 Time reduced (to 13:54:23) due to upcoming event (msgmaint) on Mon Oct 26 2020 05:00 am

    The problem is - in SCFG, MSGMAINT is configured to run on Sunday, not Monday, and it appears it already ran:

    I imagine that's because of this code in data.cpp:
    if(tm.tm_mday==last_tm.tm_mday && tm.tm_mon==last_tm.tm_mon)
    thisevent+=24L*60L*60L; /* already ran today, so add 24hrs */

    Assuming it's going to run again 24 hours later isn't always going to be correct.

    Oct 25 05:00:00 p-1-1 synchronet: evnt MSGMAINT Waiting for node 1 to run timed event: MSGMAINT
    Oct 25 05:00:00 p-1-1 synchronet: evnt MSGMAINT Waiting for all nodes to become inactive before running timed event
    Oct 25 05:00:01 p-1-1 synchronet: evnt MSGMAINT Running native timed event: MSGMAINT

    (This is a 2 week old build of SBBS).

    I imagine that bug has been there 20 or 30 years now. :-)
    --
    digital man

    Synchronet/BBS Terminology Definition #20:
    DOCSIS = Data Over Cable Service Interface Specification
    Norco, CA WX: 61.4øF, 82.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From deon@VERT/ALTERANT to Digital Man on Sun Oct 25 15:39:00 2020
    Re: MSGMAINT
    By: Digital Man to deon on Sat Oct 24 2020 10:19 pm

    I imagine that's because of this code in data.cpp:
    if(tm.tm_mday==last_tm.tm_mday && tm.tm_mon==last_tm.tm_mon)
    thisevent+=24L*60L*60L; /* already ran today, so add 24hrs */

    Assuming it's going to run again 24 hours later isn't always going to be correct.
    Oct 25 15:05:37 p-1-1 synchronet: term Node 2 <deon> Node 2 Time reduced (to 13:54:23) due to upcoming event (msgmaint) on Mon
    Oct 26 2020 05:00 am

    I imagine that bug has been there 20 or 30 years now. :-)

    Oh wow...

    Yeah, it would make sense if in the 24hrs before the event (or more specifically, in the mins before the event that I could potentially still be on, because my time limit permits me), I get that warning, but not after it.

    ...ëîåï

    ... One does not thank logic. Sarek, Journey to Babel, stardate 3842.4.

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!