Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 32760  |
|  Digital Man to Nightfox  |
|  Re: Using JSexec to run IRCd  |
|  18 Nov 25 22:25:05  |
 
TZUTC: -0800
MSGID: 58892.sync_sys@1:103/705 2d837ecd
REPLY: 58885.sync_sys@1:103/705 2d82e7d4
PID: Synchronet 3.21a-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0
TID: SBBSecho 3.32-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
FORMAT: flowed
NOTE: FSEditor.js v1.105
Re: Re: Using JSexec to run IRCd
By: Nightfox to Dan Clough on Tue Nov 18 2025 11:30 am
> In addition to the services, things like displaying the external programs
> menu and letting the user change their user settings are done in JS now, I
> believe (xtrn_sec.js and user_settings.js, respectively). There are command
> shells in JS too, and I'm sure there are other things that are done with JS.
Yeah, but the triggers (for crashes in the JS engine) seem to be triggered by
a lot of JS runtime, context, and object creations, which are hard to do using
the terminal server. So, much of the JS-related crashes seem to stem from a
lot of web or services connections and requests, potentially exhausting
resources or hitting concurrency problems.
--
digital man (rob)
Sling Blade quote #8:
Karl Childers: I don't reckon I got no reason to kill nobody.
Norco, CA WX: 49.4øF, 84.0% humidity, 0 mph E wind, 0.01 inches rain/24hrs
--- SBBSecho 3.32-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 601 610 700 840
SEEN-BY: 218/860 880 226/30 227/114 229/110 112 206 317 400 426 428
SEEN-BY: 229/470 700 705 266/512 280/464 291/111 301/1 320/219 322/757
SEEN-BY: 342/200 396/45 460/58 633/280 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426
|
[ << oldest | < older | list | newer > | newest >> ]