I have a user that is connecting via an Atari ST using VT52 emulation. He is complaining that he keeps getting timed out. I have triple checked my settings for user inactivity timeouts and have asked other users, but this is the only user that is having this issue. And it only is when they are using VT52. Can someone please provide me some "path" to look down to resolve this?
Re: VT52 timeout
By: mhansel739 to All on Thu Jun 01 2023 02:42 am
I have a user that is connecting via an Atari ST using VT52 emulation. He is complaining that he keeps getting timed out. I have triple checked my settings for user inactivity timeouts and have asked other users, but this is the only user that is having this issue. And it only is when they are using VT52. Can someone please provide me some "path" to look down to resolve this?
Check your terminal server log output. Do you see "terminal not detected, reducing inactivity hang-up timeout to x"? If so, this is a feature of exec/login.js, controlled via the [login] inactive_hangup option in ctrl/modopts.ini file.
BTW, once the dumb-terminal user authenticates (logs-in) to BBS successfully, their inactivity timeout setting should revert to the same/normal inactivity setting you have set in SCFG for all users.
In my opinion, showing those Minesweeper stats (or anything external) is what's setting the inactivity correctly while Matt's board doesn't have
Re: VT52 timeout
By: Digital Man to mhansel739 on Thu Jun 01 2023 04:13 pm
BTW, once the dumb-terminal user authenticates (logs-in) to BBS successfully, their inactivity timeout setting should revert to the same/normal inactivity setting you have set in SCFG for all users.
Just tested this on bbs.synchro.net. After logging in, it shows the Synchronet ANSI and a pause prompt. If I sit at that prompt, it will time me out in 30 seconds.
If I continue past that and sit at the pause prompt after
the Minesweeper stats, it does not time me out and seems to be using the longer inactivity setting.
In my opinion, showing those Minesweeper stats (or anything external) is what's setting the inactivity correctly while Matt's board doesn't have something like that loading to "reset" the setting.
Re: VT52 timeout
By: Phigan to Digital Man on Fri Jun 02 2023 07:05 am
In my opinion, showing those Minesweeper stats (or anything external) is what's setting the inactivity correctly while Matt's board doesn't have
Actually, Matt's board does have something showing after login.. a weather display. Still, it may not be doing something that the Minesweeper call is doing.
A strange difference is that on bbs.synchro.net, there is a beep at 15 seconds and then hangup/timeout at 30 seconds. On Matt's board, both the beep and the hangup happen at 30 seconds.
Are you sure about that? The 30 second login inactivity timeout on Vertrauen is only in effect for non-ANSI/PETSCII/UTF-8 terminals, so you woudn't be shown an ANSI. The login inactivity timer on Vertrauen for ANSI, PETSCII, and UTF-8 detected terminals is 5 minutes.
No, the inactivity timer is (re)set (to whatever the sysop has set in SCFG->System->Advanced->Max User Inactivity) right after the user is authenticated.
Re: VT52 timeout
By: Digital Man to Phigan on Fri Jun 02 2023 11:58 am
Are you sure about that? The 30 second login inactivity timeout on Vertrauen is only in effect for non-ANSI/PETSCII/UTF-8 terminals, so you woudn't be shown an ANSI. The login inactivity timer on Vertrauen for ANSI, PETSCII, and UTF-8 detected terminals is 5 minutes.
Positive. Synchronet is detecting me as US-ASCII w/ ANSI (vs CP437 w/ ANSI)
and I'm getting the shorter inactivity upon connect, through login, right up until the minesweeper stats. The Synchronet ANSI isn't shown with upper ASCII characters, it replaces a lot of them with *s or @s or various standard ASCII ones.
No, the inactivity timer is (re)set (to whatever the sysop has set in SCFG->System->Advanced->Max User Inactivity) right after the user is authenticated.
Well, it's not _right_ after, or I wouldn't get disconnected at that pause prompt after 30 seconds. But let's see what Matt says he has set in that location. On his board it happens to me even at the main menu. Same settings/configuration as when connecting to Vertrauen.
"TERM: 80x24 US-ASCII / DUMB"
I haven't been able to reproduce anything other than expected behavior here: non-ANSI/RIP/PETSCII/UTF-8 terminals are disconnected after 30 seconds of inactivity before authenticating. All other terminals (and authenticated users) are allowed 10 minutes of inactivity.
Re: VT52 timeout
By: Digital Man to Phigan on Sun Jun 04 2023 08:40 pm
"TERM: 80x24 US-ASCII / DUMB"
What's happening to me is that when I initially connect I get this above. Everything is black and white, and I'm in "dumb" mode.
If I press enter once on the login prompt, it changes to color.
I think this
is the point where I'm getting US-ASCII / ANSI. Note where you showed my setting as "Auto". I'm not forcing US-ASCII.
When I log in from another
terminal, it correctly detects and says "Auto CP437 / ANSI".
Re: VT52 timeout
By: Digital Man to Phigan on Sun Jun 04 2023 08:40 pm
I haven't been able to reproduce anything other than expected behaviorhere:
non-ANSI/RIP/PETSCII/UTF-8 terminals are disconnected after 30 seconds of inactivity before authenticating. All other terminals (and authenticated users) are allowed 10 minutes of inactivity.
Ok, but neither Matt nor I are saying something to the contrary of this.
We're saying that on his BBS, non-ANSI/RIP/PETSCII/UTF-8 terminals are disconnected after 30 seconds of inactivity even after authenticating. He hasn't answered about what he has in that inactivity timeout field you mentioned in scfg yet.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,056 |
| Nodes: | 17 (0 / 17) |
| Uptime: | 14:01:01 |
| Calls: | 501,034 |
| Files: | 109,384 |
| D/L today: |
88 files (33,960K bytes) |
| Messages: | 304,997 |