I have a login on one of my nodes that ais "stuck". Yesterday when I was testing stuff the terminal-program I used crashed when transfering a file,
and now the users is logged on and it says "Transfering files" in MIS. Restarting MIS and Mystic doesn't seem to help...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: CoL Unl. (21:1/999)

I have a login on one of my nodes that ais "stuck". Yesterday when I was testing stuff the terminal-program I used crashed when transfering a
file, and now the users is logged on and it says "Transfering files" in MIS. Restarting MIS and Mystic doesn't seem to help...

Load nodespy and press enter on the user and select "Kill Ghost Node".

--- Mystic BBS v1.12 A36 2017/11/16 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/17/17, Scuttle said the following...

I have a login on one of my nodes that ais "stuck". Yesterday when I was testing stuff the terminal-program I used crashed when transfering a
file, and now the users is logged on and it says "Transfering files" in MIS. Restarting MIS and Mystic doesn't seem to help...

run nodespy, arrow to the stuck node, hit enter, go down and Kill Ghost (enter). Then you can exit nodespy with ESCs.

--- Mystic BBS v1.12 A36 2017/11/15 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

I have a login on one of my nodes that ais "stuck". Yesterday when I testing stuff the terminal-program I used crashed when transfering a file, and now the users is logged on and it says "Transfering files" MIS. Restarting MIS and Mystic doesn't seem to help...

run nodespy, arrow to the stuck node, hit enter, go down and Kill Ghost (enter). Then you can exit nodespy with ESCs.

i've been running into a similar situation here, i'm guessing that its
because of all the telnet scanners out there. nodespy says that the nodes are empty, but mis2 says that there are users signed in. so, i can't kill what i can't see and the only option is to restart mis2.

|08\ |07H7|08 of |07Blocktronics/dIVINE sTYLERS!/aCCESSiON/TRSi/Break!Ascii |08\ |07Haciend bbs sysop |08(|15telnet://haciend.com|08)|07

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Haciend.com | Scandinavian demoscene bbssince 1996 (21:1/155)

On 11/25/17, h7 said the following...

i've been running into a similar situation here, i'm guessing that its because of all the telnet scanners out there. nodespy says that the
nodes are empty, but mis2 says that there are users signed in. so, i
can't kill what i can't see and the only option is to restart mis2.

You should be able to see them with nodespy, G00r00 is taking about rolling that in to mis2 and including a command line kill ghost. Right now you can generally 'see' them in 'ps a' and kill their PID# from there (in Linux), but can't really tell it's a ghost except by it being there a long time.

--- Mystic BBS v1.12 A36 2017/11/23 (Linux/32)
* Origin: BCW Livingroom (21:1/145.5)

i've been running into a similar situation here, i'm guessing that its because of all the telnet scanners out there. nodespy says that the
nodes are empty, but mis2 says that there are users signed in. so, i
can't kill what i can't see and the only option is to restart mis2.

I think this might just be a display bug in MIS2 that I recently fixed in the latest pre-alpha.

--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I think this might just be a display bug in MIS2 that I recently fixed
in the latest pre-alpha.

i wish it were so, telnet says busy when i try to dial in during that error.

|08\ |07H7|08 of |07Blocktronics/dIVINE sTYLERS!/aCCESSiON/TRSi/Break!Ascii |08\ |07Haciend bbs sysop |08(|15telnet://haciend.com|08)|07

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Haciend.com | Scandinavian demoscene bbssince 1996 (21:1/155)