A user has logged into my BBS, read a message in DDMR and then the session has hung. Over an hour later session is still active.
I used umonitor to spy on user's session, selected [Q]uit, user back to main menu, then after a few minutes sbbs booted the user off due to inactivity.
DDMR should also boot users off due to inactivity.
DDMR should also boot users off due to inactivity.
Try to find out what terminal was being used.
I made a fix yesterday (as it indeed seemed to be a bug in DDMessageReader) which should fix the issue. Basically, the issue was that there's a function that lets the user scroll up & down through a set of text lines (which is used for reading a message with the scrollable interface), and it apparently wasn't properly checking for getting no user input (which indicates an input timeout occurred).
Codefenix wrote to Nightfox <=-
Re: DDMsgReader - Inactivity timer does not seem to work when reading mes
By: Nightfox to Codefenix on Thu Dec 19 2024 09:58 am
I made a fix yesterday (as it indeed seemed to be a bug in DDMessageReader) which should fix the issue. Basically, the issue was that there's a function that lets the user scroll up & down through a set of text lines (which is used for reading a message with the scrollable interface), and it apparently wasn't properly checking for getting no user input (which indicates an input timeout occurred).
Very nice! I can confirm the the behavior I observed while using DDMR & IcyTerm is no longer happening.
However, IcyTerm (0.7.8) still likes to randomly drop carrier, mainly
with Sync boards for some reason. That's obviously a whole other issue
and isn't DDMR's problem though :D
Codefenix wrote to Nightfox <=-
Re: DDMsgReader - Inactivity timer does not seem to work whenreading
mes By: Nightfox to Codefenix on Thu Dec 19 2024 09:58 am
I made a fix yesterday (as it indeed seemed to be a bug in DDMessageReader) which should fix the issue. Basically, the issuewas
that there's a function that lets the user scroll up & down through aset
of text lines (which is used for reading a message with thescrollable
interface), and it apparently wasn't properly checking for getting nouser
input (which indicates an input timeout occurred).
Very nice! I can confirm the the behavior I observed while using DDMR&
IcyTerm is no longer happening.
However, IcyTerm (0.7.8) still likes to randomly drop carrier, mainly with Sync boards for some reason. That's obviously a whole otherissue
and isn't DDMR's problem though :D
Does IcyTerm do anything that SyncTerm (or NetRunner) don't do? If not, why use it?
Does IcyTerm do anything that SyncTerm (or NetRunner) don't do? If not, why use it?
Does IcyTerm do anything that SyncTerm (or NetRunner) don't do? If not,
why use it?
Personally I prefer SyncTERM and don't really care about IcyTerm at all.
But when users make the claim that my board is locking up on them whenever using that particular terminal, then that's something I want to understand. Especially when said terminal is gaining in popularity.
Sysop: | Tetrazocine |
---|---|
Location: | Melbourne, VIC, Australia |
Users: | 4 |
Nodes: | 8 (0 / 8) |
Uptime: | 59:03:02 |
Calls: | 65 |
Files: | 21,500 |
Messages: | 73,556 |