From: daryl.stout@TBOLT.remove-6ev-this

To: DIGITAL MAN
Rob,

I know you have it set where if a terminal (i.e. SyncTerm) isn't
detected (it's usually a bot), the inactivity timeout is reduced to 75
seconds. I did save a message about where that data is...but is it
possible to change the variable to lower that timeout for these idiots??

Daryl

---
þ OLX 1.53 þ Are cranberries healthy?? I never heard one complain.
þ Synchronet þ DoveNet: The Thunderbolt BBS - wx1der.dyndns.org
--- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-b9s-this

To: Daryl Stout
Re: CHANGING TIMEOUT
By: Daryl Stout to DIGITAL MAN on Sun Mar 25 2018 09:50 am

Rob,

I know you have it set where if a terminal (i.e. SyncTerm) isn't
detected (it's usually a bot), the inactivity timeout is reduced to 75 seconds. I did save a message about where that data is...but is it
possible to change the variable to lower that timeout for these idiots??

SCFG->Nodes->Node 1->Advanced Options->Inactivity Disconnection. The default is 600 seconds, which means the non-ANSI terminal will have a hangup/timeout of 150 seconds (25% of 600).

digital man

This Is Spinal Tap quote #41:
Ian Faith: It say's "Memphis show cancelled due to lack of advertising funds." Norco, CA WX: 58.9øF, 57.0% humidity, 6 mph NE wind, 0.00 inches rain/24hrs
--- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-m4j-this

To: Daryl Stout
Re: CHANGING TIMEOUT
By: Daryl Stout to DIGITAL MAN on Sun Mar 25 2018 10:05 pm

Rob,

SCFG->Nodes->Node 1->Advanced Options->Inactivity Disconnection. The default DM>600 seconds, which means the non-ANSI terminal will have a hangup/timeout of DM>150 seconds (25% of 600).

I noticed my settings are 180 seconds for the inactivity warning, and
300 seconds for a disconnection. So, that explains why my values are as
they are. I thought it was something in the script.

The "25%" comes from the script.

digital man

Synchronet/BBS Terminology Definition #50:
SSJS = Server-side JavaScript
Norco, CA WX: 51.5øF, 66.0% humidity, 5 mph ESE wind, 0.00 inches rain/24hrs --- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: daryl.stout@TBOLT.remove-b0-this

To: DIGITAL MAN
Rob,

SCFG->Nodes->Node 1->Advanced Options->Inactivity Disconnection. The default DM>600 seconds, which means the non-ANSI terminal will have a hangup/timeout of DM>150 seconds (25% of 600).

I noticed my settings are 180 seconds for the inactivity warning, and
300 seconds for a disconnection. So, that explains why my values are as
they are. I thought it was something in the script.

Daryl

---
þ OLX 1.53 þ Bad Restaurant: Hospital map on the back of the menu.
þ Synchronet þ DoveNet: The Thunderbolt BBS - wx1der.dyndns.org
--- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-km7-this

To: mark lewis
Re: CHANGING TIMEOUT
By: mark lewis to Digital Man on Mon Mar 26 2018 02:44 pm

On 2018 Mar 25 13:02:02, you wrote to Daryl Stout:

I know you have it set where if a terminal (i.e. SyncTerm) isn't
detected (it's usually a bot), the inactivity timeout is reduced to 75
seconds. I did save a message about where that data is...but is it
possible to change the variable to lower that timeout for these
idiots??

SCFG->Nodes->Node 1->Advanced Options->Inactivity Disconnection. The default is 600 seconds, which means the non-ANSI terminal will have a hangup/timeout of 150 seconds (25% of 600).

so if i'm doing the math properly, if he wants a 30 second drop time for the bots, he'd want to put 240 as his "inactivity disconnect" time out, right? 25% of that is 60 and half of that is 30...

25% of 120 is 30.

digital man

Synchronet "Real Fact" #17:
"Vertrauen" (ver-trow-en) translates to "trust" in German, and was a band name. Norco, CA WX: 61.8øF, 44.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs
--- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: mark.lewis@1:3634/12.73.remove-km7-this

To: Digital Man

On 2018 Mar 25 13:02:02, you wrote to Daryl Stout:

I know you have it set where if a terminal (i.e. SyncTerm) isn't
detected (it's usually a bot), the inactivity timeout is reduced to 75
seconds. I did save a message about where that data is...but is it
possible to change the variable to lower that timeout for these
idiots??

SCFG->Nodes->Node 1->Advanced Options->Inactivity Disconnection. The default is 600 seconds, which means the non-ANSI terminal will have a hangup/timeout of 150 seconds (25% of 600).

so if i'm doing the math properly, if he wants a 30 second drop time for the bots, he'd want to put 240 as his "inactivity disconnect" time out, right? 25% of that is 60 and half of that is 30...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Always hunt with impeccable spirit. The animals will respond accordingly. ---
* Origin: (1:3634/12.73)
--- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: mark.lewis@1:3634/12.73.remove-ith-this

To: Digital Man

On 2018 Mar 26 12:20:26, you wrote to me:

SCFG->Nodes->Node 1->Advanced Options->Inactivity Disconnection. The
default is 600 seconds, which means the non-ANSI terminal will have
a hangup/timeout of 150 seconds (25% of 600).

so if i'm doing the math properly, if he wants a 30 second drop time
for the bots, he'd want to put 240 as his "inactivity disconnect"
time out, right? 25% of that is 60 and half of that is 30...

25% of 120 is 30.

i was trying to follow your writing above with the other information available...

default 600 seconds
non-ANSI termination 150
where'd the 75 come from that we see as in below? is it not the 150 divided in half?


Mar 28 11:49:05 haven synchronet: term 0031 Telnet connection accepted from: 111.243.7.207 port 42418
Mar 28 11:49:05 haven synchronet: term Node 1 attached to local interface 192.168.xxx.xxx port xxxxx
Mar 28 11:49:05 haven synchronet: term Node 1 11:49 Wed Mar 28 2018
Node 1
Mar 28 11:49:05 haven synchronet: term Node 1 Telnet <no name> [111.243.7.207] Mar 28 11:49:11 haven synchronet: term Node 1 Terminal not detected, reducing inactivity hang-up timeout to 75 seconds
Mar 28 11:49:42 haven synchronet: term Node 1 disconnected
Mar 28 11:49:44 haven synchronet: term Node 1 thread terminated (0 node threads remain, 150 clients served)


so i figured it backwards 75 is half of 150 and 150 is 1/4th of 600...

600 * .25 = 150
150 / 2 = 75 for non-ANSI bot termination

so, for the example i gave...

240 * .25 = 60
60 / 2 = 30 for non-ANSI bot termination

[EDIT]

ahh... i see what i did... i didn't know that max had reduced the default timeout to 300 seconds in her setup :oops:

sorry 'bout that :?


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Where there's a will... there's a relative.
---
* Origin: (1:3634/12.73)
--- Synchronet 3.17a-Win32 NewsLink 1.108
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)