TZUTC: -0700
MSGID: 11166.bbs_carn@1:103/705 2892082a
REPLY: 11165.bbs_carn@1:103/705 2891fdf7
PID: Synchronet 3.20a-Linux master/0f4325eec Apr  3 2023 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/fcf4a0012 Apr  4 2023 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
NOTE: FSEditor.js v1.104
  Re: BBS Software Timeout Values
  By: Jas Hud to Rob Swindell on Tue Apr 04 2023 04:39 pm

 >   To: Rob Swindell
 >   Re: BBS Software Timeout Values
 >   By: Rob Swindell to Dennis Scott on Tue Apr 04 2023 09:56 am
 >
 >
 >  > Nodes are a finite resource. Sysops don't want their systems to be
 >  > subject to very simple "denial of service" attacks by users either
 >  > accidentally or purposefully just "walking away from the keyboard" once
 >  > connected and tying up all their nodes.
 >
 > on datastream which was a very popular gaming bbs, i had some games rigged
 > to not kick the user due to running out of time.
 >
 > these people would rot on there for many, many hours.
 > some of them were using tradewars trainer programs and that screwed up.
 >
 > i think a 5 min inactivity time out is decent.

I think in that example (e.g. a TradeWars trainer/bot running amock), a total
timeout is good to enforce too. A bot can keep a node active, but not doing
anything "useful" for a really long time.
-- 
                                            digital man (rob)

Sling Blade quote #4:
Doyle: wimpy-ass kids or mental retards.. she got one of each livin' with her.
Norco, CA WX: 60.7øF, 26.0% humidity, 6 mph SSW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 1/123 10/0 1 15/0 18/200 90/1 102/401 103/1 705 105/81 106/201
SEEN-BY: 123/131 129/305 153/7715 214/22 218/0 1 215 501 700 720 810
SEEN-BY: 218/820 840 850 860 880 226/30 227/114 229/110 111 112 113
SEEN-BY: 229/206 275 307 317 400 424 426 428 452 470 550 664 700 266/512
SEEN-BY: 280/464 282/1038 301/1 317/3 320/219 322/757 342/200 396/45
SEEN-BY: 460/58 633/280 712/848
PATH: 103/705 218/700 229/426