Hi there

[snip]

0:36:13 EVENT Sending shutdown notice to node: 2
0:36:13 EVENT Resetting ghost node: 2 (Invalid server slot)
0:36:13 EVENT Sending shutdown notice to node: 4
0:36:13 EVENT Resetting ghost node: 4 (Invalid server slot)

[snip]

What I'm finding is that if I run a few local logins in order to do some
tests etc. MIS will close them down on me after a certain period of time. Is there somewhere I can alter that setting so I am not re-spawning nodes that
are being shuttered on me?

Perhaps a switch could be added along the lines of Mystic -l -g (login local, ignore ghost node rules) or similar?

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 14 Apr 2019, Avon said the following...

What I'm finding is that if I run a few local logins in order to do some tests etc. MIS will close them down on me after a certain period of
time. Is there somewhere I can alter that setting so I am not
re-spawning nodes that are being shuttered on me?

Perhaps a switch could be added along the lines of Mystic -l -g (login local, ignore ghost node rules) or similar?

Might be a good idea, I know that won't be the only thing that does that - I've had hangs and hangups since the start due to time-out that are hidden
or not changeable. I don't know what it is or where, but I do know the time out you mean and ghost node killing has made that happen better in a way,
at least it really does kill ghost nodes now (which is good), but will time you out.
So the idea of an added switch would be a good idea to allow changes to the timeout that node killing uses. I think the 'period of time' is the original
5 minute timeouts. What happened to me since I first changed time limits up
is the nodes will hang until the full timeout occurs and then kill them as ghost nodes (which they are at that time). So there's good and bad to what it's up to - the good is being better at killing ghost nodes.

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

I saw your post to g00r00 on Restting Ghost Nodes with your example. I know I've seen hidden timeouts in the past, but in the testing I did this morning they are gone. g00r00 has found most if not all in A43 and I've gone up to
14 minutes without a hang or timeout if any kind on my AlphaTest system which is Ubuntu 16.04.6 LTS right now. I have the General Settings Inactivity set
to 999 (~25 minutes) and have gone up to 14 minutes with no issues so far. That being said I was using nodespy on the BBS itself, they may exist if I
do things a different way. You mentioned Mystic -l -g to block the Ghost
rule timeout.
That implies to me Windows, were you using Windows 7 or 10 and were you
using Mystic -l to do the logins?
I'm trying to recreate the issue your seeing and haven't been able to so far. It needs to be nailed down and repeatable if g00r00 has any hope of finding
it as you know. My method of testing was to use nodespy logging in locally and just sitting in the Main Menu for whatever number of minutes, then hitting A to test that menu functions. What are you doing?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 14 Apr 2019 at 09:54a, bcw142 pondered and said...

That implies to me Windows, were you using Windows 7 or 10 and were you using Mystic -l to do the logins?

yes windows 7 and mystic -l

minutes, then hitting A to test that menu functions. What are you doing?

as per above, thanks for looking into it.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 15 Apr 2019, Avon said the following...

On 14 Apr 2019 at 09:54a, bcw142 pondered and said...

That implies to me Windows, were you using Windows 7 or 10 and were y using Mystic -l to do the logins?

yes windows 7 and mystic -l

OK, I will play with my Window7 and the Pi to see if I spot anything. I know 64 bit Linux is working fine, but will try the same testing with mystic -l
to make sure. I've already found issues with login under Windows7, my guess
is that it's another Windows7 thing. The Pi is the only other 32 bit system
I have running at the moment and what I run my main BBS on.

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)