I still can't seem to prove the u ACS is working with the latest build 04/13

Flags, groups and sec levels do seem to work just echonode ID is not playing nice. Can yo confirm your copy works and also the ACS flag to use is u ?

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

Flags, groups and sec levels do seem to work just echonode ID is not playing nice. Can yo confirm your copy works and also the ACS flag to
use is u ?

I never got a chance to look at it the other day.

I did look at it just now and I think I have it fixed up. I'll upload a new Windows build for you in a few minutes. It'll be there by the time you see this :)

--- Mystic BBS v1.12 A39 2018/04/14 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 04/14/18, g00r00 pondered and said...

Flags, groups and sec levels do seem to work just echonode ID is not playing nice. Can yo confirm your copy works and also the ACS flag to use is u ?

I never got a chance to look at it the other day.

I did look at it just now and I think I have it fixed up. I'll upload a new Windows build for you in a few minutes. It'll be there by the time you see this :)

--- Mystic BBS v1.12 A39 2018/04/14 (Windows/32)

Thanks, pulled a copy just now but will grab another in 15 mins, just heading out to do a Dad's Taxi run for my son.

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

Thanks, pulled a copy just now but will grab another in 15 mins, just heading out to do a Dad's Taxi run for my son.

You probably have the right one, I think I uploaded it as my BBS was sending the packet to you!

You'll want to upgrade not just for the "U" ACS fix but also because I may have finally smashed what I hope to be the lone remaining crash issue with the new server.

I was finally able to reproduce a crash on my Linux BBS randomly (but consistently?), and I fixed that up today. I wasn't able to get it to crash after that with 250 concurrent telnet users active on the BBS after 140,000 connections.

I may set it up tonight before bed and let it run all day which would
probably hit around a million connections. If it hits that, then I'm pretty sure we're good lol

--- Mystic BBS v1.12 A39 2018/04/14 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 04/14/18, g00r00 pondered and said...

You probably have the right one, I think I uploaded it as my BBS was sending the packet to you!

v1.12 A39 Windows/32 Compiled 2018/04/14 22:27:36 has been applied to 1/100 3/100 and 1/101 I'll leave Solaris and Dan to do 2/100 and 4/100 respectively.

You'll want to upgrade not just for the "U" ACS fix but also because I
may have finally smashed what I hope to be the lone remaining crash
issue with the new server.

Confirming U eacs is now working as intended. Noted label change too. List implies read - correct?

Good stuff on the server bugs, will let you know if anything pops up at this end.

I was finally able to reproduce a crash on my Linux BBS randomly (but consistently?), and I fixed that up today. I wasn't able to get it to crash after that with 250 concurrent telnet users active on the BBS
after 140,000 connections.

That's a healthy soak test!

I may set it up tonight before bed and let it run all day which would probably hit around a million connections. If it hits that, then I'm pretty sure we're good lol

Coolio. I am prodding Areafix some more before bed if I spot anything I'll
post it here.

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/14 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)