Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 32729  |
|  Nightfox to Digital Man  |
|  Using JSexec to run IRCd  |
|  16 Nov 25 13:50:08  |
 
TZUTC: -0800
MSGID: 58854.sync_sys@1:103/705 2d8067d9
REPLY: 58852.sync_sys@1:103/705 2d7f2284
PID: Synchronet 3.21a-Linux master/efc0fbb26 Nov 09 2025 GCC 13.3.0
TID: SBBSecho 3.32-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0
COLS: 80
BBSID: DIGDIST
CHRS: CP437 2
FORMAT: flowed
NOTE: SlyEdit 1.92e (2025-11-11) (ICE style)
Re: Using JSexec to run IRCd
By: Digital Man to Nightfox on Sat Nov 15 2025 03:02 pm
>> In Linux, you can run umonitor to show node status & such - it's sort of
>> similar to what the Windows GUI shows, though it's not everything. There's
>> also gtkmonitor for Linux too.
DM> I not clear how umonitor or SBBSCTRL ("the Windows GUI") helps with
DM> monitoring the IRCd though. Since the ircd.js is a *static* service, it
DM> handles its own listening/answering of incoming connections and everything
DM> it logs (e.g. to syslog or the "Services" windows of SBBSCTRL) would also
DM> be sent to the console when run via JSexec.
I hadn't closely followed the whole thread.. When I replied, I thought they
may have generally been looking for some kind of monitoring application for
Linux.
Nightfox
---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757
SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114
SEEN-BY: 229/110 112 206 317 400 426 428 470 700 705 240/1120 5832
SEEN-BY: 263/1 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 633/267
SEEN-BY: 633/280 384 410 414 418 420 422 2744 712/848 770/1 902/26
SEEN-BY: 5020/400 5075/35
PATH: 103/705 280/464 633/280 229/426
|
[ << oldest | < older | list | newer > | newest >> ]