• Possible bug found

    From Christian Sacks@2:250/5 to g00r00 on Mon Nov 29 05:36:31 2021
    [also posted in ARK_MYS]

    Hey g00r00, hope you're well.

    I think I may have found a bug but wanted to ask you just in case there's a reason why I see what I see and I didn't realise.

    I open two connections to my BBS, via SSH and I'm on node#1, via TELNET and
    I'm on node#2.

    On node#1 my time left says 9718 mins
    On node#2 my time left says 9972 mins

    By default I give the sysop just 9999 mins per day which I know is insane as there's only 1440 mins in a day, but 9999 feels "l33t" lol.

    Anyway, why do I see different amounts of time left per node/connection type? Thanks in advance.

    ... The person who snores the loudest will fall asleep first
    --- Mystic BBS v1.12 A47 2021/08/10 (Linux/64)
    * Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (2:250/5)
  • From g00r00@1:129/215 to Christian Sacks on Mon Nov 29 11:35:04 2021
    I think I may have found a bug but wanted to ask you just in case
    there's a reason why I see what I see and I didn't realise.

    I open two connections to my BBS, via SSH and I'm on node#1, via TELNET and I'm on node#2.

    On node#1 my time left says 9718 mins
    On node#2 my time left says 9972 mins

    I think this might be more of a side effect of how the time system works, not a bug. In 1995 or so I had no consideration that there would be the same user logged into multiple nodes at the same time, so each node's time left operates independant of the other one.

    For example: If you log into node 1 with 9000 minutes and wait 10 minutes, you'll have 8990 minutes left node 1. But that time left information isnt saved to the user database until you log off or run an external program. If you then log into node 2 while you're still on node 1, that node will start again with 9000 minutes because the data was never saved. Now you'll have 8990 on node 1 and 9000 on node 2.

    A similar thing happens when you log off or run a door. If you log off on node 1 with 8990 minutes left it will be saved. But then if you log off right after that on node 2 with 9000 minutes left, that will be saved and it will overwrite the 8990.

    Hope that helps explain. If you think its not that and something else is happening let me know.

    By default I give the sysop just 9999 mins per day which I know is
    insane as there's only 1440 mins in a day, but 9999 feels "l33t" lol.

    You can also turn off the time per day system entirely if you really wanted to but I don't know how that factors into the l33t feels! lol :)

    ... Live every day as though it were your last. One day, you'll be right

    --- Mystic BBS v1.12 A47 2021/11/24 (Windows/64)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)
  • From Christian Sacks@2:250/5 to g00r00 on Tue Nov 30 14:26:26 2021
    On 29 Nov 2021, g00r00 said the following...

    I think I may have found a bug but wanted to ask you just in case there's a reason why I see what I see and I didn't realise.

    I open two connections to my BBS, via SSH and I'm on node#1, via TELN and I'm on node#2.

    On node#1 my time left says 9718 mins
    On node#2 my time left says 9972 mins

    I think this might be more of a side effect of how the time system
    works, not a

    bug. In 1995 or so I had no consideration that there would be the same user logged into multiple nodes at the same time, so each node's time left operates independant of the other one.

    For example: If you log into node 1 with 9000 minutes and wait 10
    minutes, you'll have 8990 minutes left node 1. But that time left information isnt saved to the user database until you log off or run an external program. If you then log into node 2 while you're still on
    node 1, that node will start again with 9000 minutes because the data
    was never saved. Now you'll have 8990

    on node 1 and 9000 on node 2.

    A similar thing happens when you log off or run a door. If you log off
    on node

    1 with 8990 minutes left it will be saved. But then if you log off
    right after

    that on node 2 with 9000 minutes left, that will be saved and it will overwrite

    the 8990.

    Hope that helps explain. If you think its not that and something else
    is happening let me know.

    Ah yes, perfect. I just tried from no logins, and connecting twice at the same time, and both logged in "me" had the same time left, so it ties in exactly to what you said above. That puts that to bed I guess then, thanks for the help.

    By default I give the sysop just 9999 mins per day which I know is insane as there's only 1440 mins in a day, but 9999 feels "l33t" lol.

    You can also turn off the time per day system entirely if you really wanted to but I don't know how that factors into the l33t feels! lol :)

    Um, no. I want the time per day system, feels more traditional, and yes the l33t factor is honoured by having it :P

    ... Live every day as though it were your last. One day, you'll be right

    Deep, hard truth. Hope we all got many decades left.

    ... Light year: 1/3 less calories than your regular year
    --- Mystic BBS v1.12 A47 2021/08/10 (Linux/64)
    * Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (2:250/5)