I believe I have observed sbbs hang, probably when I disconnect
accidentally without logging off. The process seems to start taking memory
and cpu cycles. Is there a recommended way to try and clear these
processes (I guess the best way is to avoid disconnecting abruptly, and incorrect). But I've seen load go > 20 on server and slow everything down.

Any suggestions appreciated.
---
Amessyroom
toolazy.synchro.net:2323 (telnet)

Re: sbbs process hanging on linux
By: Amessyroom to All on Wed Sep 10 2025 08:47 pm

I believe I have observed sbbs hang, probably when I disconnect
accidentally without logging off. The process seems to start taking memory and cpu cycles. Is there a recommended way to try and clear these
processes (I guess the best way is to avoid disconnecting abruptly, and incorrect). But I've seen load go > 20 on server and slow everything down.

Any suggestions appreciated.

Watch the log output to see what's happening when you "disconnect abruptly". What you're describing doesn't sound like anything that has been reported or observed by myself.
--
digital man (rob)

Synchronet "Real Fact" #39:
Synchronet first supported Windows NT v6.x (a.k.a. Vista/Win7) w/v3.14a (2006) Norco, CA WX: 64.1øF, 84.0% humidity, 1 mph NW wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

I believe I have observed sbbs hang, probably when I disconnect
accidentally without logging off. The process seems to start taking memory and cpu cycles. Is there a recommended way to try and clear these
processes (I guess the best way is to avoid disconnecting abruptly, and incorrect). But I've seen load go > 20 on server and slow everything down.

Any suggestions appreciated.

When I have seen this, it is unrelated to how someone disconnects from the
BBS, so it might or might not be of any assistance but here goes...

binkit will peg a CPU at 100% if it gets hung. It is supposed to time out
if a connection gets hung but doesn't always do so. I reported it a couple of times and it was supposedly "fixed" but then later it will start doing it again. After the third time I quit using it.

My suggestions are:

(1) check and make sure an inbound or outbound binkit connection is not hung (2) if the issue persists, stop using binkit and use binkd instead

Bear in mind that, if you are on linux or another OS that strictly enforces user access, binkd will need to run under the same user as synchronet
in order for things to work smoothly.


* SLMR 2.1a * Speed doesn't kill. Stopping very fast kills.
---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP