From: nospam.g00r00@f215.n129.z1.binkp.net

On 21 Mar 2020, Aaron Thomas said the following...

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

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.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Aaron.Thomas@f426.n229.z1.binkp.net

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

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.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Aaron.Thomas@f426.n229.z1.binkp.net

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 3?

It's not a big deal, but it would look more orderly when displaying "Who's
On?" if the only user logged on was on Node 1.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Aaron.Thomas@f426.n229.z1.binkp.net

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

I'm using Linux. Thanks for this tip - I will read up on it and see if I can kill any unwanted processes with it.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Gryphon@f324.n106.z1.binkp.net

On 21 Mar 2020 &4, Aaron Thomas said the following...

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

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Aaron.Thomas@f426.n229.z1.binkp.net

This also doesn't consider that you could have your first 2 nodes

Thank you.

I didn't consider that until now. Maybe a significant increase in nodes is in order.

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.

A good idea also - but the problem with that is it would still stick the user in the wrong row. The other issue is that with Mystic, we still use node
number for Node Messaging.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: usenet@tracker1.dev

On 3/20/2020 3:49 PM, g00r00 wrote:

On 21 Mar 2020, Aaron Thomas said the following...

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

node

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
occupied as connections from bots... which also tends to tie things up.
Can't speak for how mystic handles connections/nodes in terms of
pre-login state, but I know I've seen this in Synchronet.

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.

--
Michael J. Ryan
@tracker1

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)