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?
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: VT52 timeout
By: Phigan to Digital Man on Fri Jun 02 2023 07:05 am

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.

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.

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.

Right. Immediately after user authentication (before any logon events, e.g. Minesweeper scores run), the inactivity timer is set to the session inactivity timeout (5 minutes).

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.

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.
--
digital man (rob)

Synchronet/BBS Terminology Definition #57:
NUP = New User Password
Norco, CA WX: 67.3øF, 67.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: VT52 timeout
By: Phigan to Digital Man on Fri Jun 02 2023 07:22 am

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.

The inactivity warning (beep in this case) is controlled by SCFG->System->Advanced->User Inactivity Warning. On Vertrauen, I have this setting set to 75 percent, so the beep happens about about 22 seconds of inactivity and the disconnect at 30.
--
digital man (rob)

Breaking Bad quote #44:
I once convinced a woman I was Kevin Costner. It worked, because I believed it Norco, CA WX: 67.3øF, 67.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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.

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: VT52 timeout
By: Phigan to Digital Man on Sun Jun 04 2023 04:50 pm

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)

Synchronet has no way of auto-detecting CP437 versus US-ASCII support in the terminal. Maybe you're logging in with a user account and your account is configured for US-ASCII terminal? If it can detect ANSI or RIP, it assumes CP437 support for the answer screen/login prompt *only*.

"TERM: 80x24 CP437 / ANSI" (as displayed before the login prompt)

If ANSI or RIP is not detect, it assumes US-ASCII:

"TERM: 80x24 US-ASCII / DUMB"

There is no situation in which the login prompt of Vertrauen should report "TERM: XxX US-ASCII / ANSI", so I think you're mistaken.

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.

That all sounds correct for a user that logins with their account configured as US-ASCII character set. Looking at your user account:
User Settings for Phigan #659:

[T] Terminal Mode : Auto US-ASCII / ANSI (color)

... confirms that. Change that to CP-437 charset and you *will* get the "upper ASCII characters" displayed to you during the logon sequence.

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.

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.
--
digital man (rob)

Synchronet/BBS Terminology Definition #33:
FSP = FidoNet Standards Proposal
Norco, CA WX: 59.9øF, 87.0% humidity, 6 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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".

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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 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.

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.

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: VT52 timeout
By: Phigan to Digital Man on Mon Jun 05 2023 11:26 am

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.

Your terminal must be sending the cursor position report (or some other ANSI escape sequence?) very late in that case.

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.

The character set is not (cannot be "Auto") for CP-437 vs US-ASCII. Only UTF-8 and PETSCII char set support can be auto-detected (kind of). Your user account on Vertrauen is forced to use US-ASCII. You can change that by using the user defaults 'T' menu option.

When I log in from another
terminal, it correctly detects and says "Auto CP437 / ANSI".

Okay. <shrug>
--
digital man (rob)

Synchronet "Real Fact" #92:
Digital Man's manifesto from '96: http://wiki.synchro.net/history:manifesto Norco, CA WX: 64.3øF, 72.0% humidity, 6 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)