I think I asked this question years ago - got an aswer, but forgot:
Is there a way to get the first user to log in on node 1 instead of node
Load up NodeSpy and see if it shows any users online that actually aren't. If you see that then highlight the node, press enter and pick "Kill Ghost
Load up NodeSpy and see if it shows any users online that actually aren If you see that then highlight the node, press enter and pick "Kill Gho
I loaded NodeSpy, but there were no ghosted users.
I tried this on a fresh install just now (which I apologize I didn't try first) and it doesn't do it. Something I've done in my customization has caused this.
My bad. If I find out what caused this, I'll post back for anyone else arriving here with this issue.
What OS are you running on? If it's Linux, I sometimes see some stuck mystic processes that have to be killed, even if nodespy doesn't show any activity on the node.
ps -ef | grep mystic
On 21 Mar 2020, Aaron Thomas said the following...node
AT> I think I asked this question years ago - got an aswer, but forgot:
AT>
AT> Is there a way to get the first user to log in on node 1 instead of
It will always start with node 1. I don't know what version you're using so I can't comment more on it, but sometimes if Mystic is shutdown incorrectly a node can be stuck as being shown online.
The MIS server should clear those up on its own after some time though.
Load up NodeSpy and see if it shows any users online that actually aren't.
If you see that then highlight the node, press enter and pick "Kill Ghost Node" which should reset it.
This also doesn't consider that you could have your first 2 nodes
Not sure if you could just configure your UI to not show the node number
at all, since aside from doors, it's about meaningless these days.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,027 |
Nodes: | 17 (0 / 17) |
Uptime: | 74:32:08 |
Calls: | 503,442 |
Calls today: | 6 |
Files: | 131,208 |
D/L today: |
426 files (117M bytes) |
Messages: | 442,163 |