OK so I came home last night and check my board and after I run my bat file for
my interbbs league I notice that it won't connect to the hub saying it is busy.
So I trying polling FSXNet and it says it is busy. Then I notice that that mutil starts to run mailin and it says it is waiting for busy nodes. So I shut down mystic, reboot the computer and same problem.
Solution: I deleted all busy semaphores from the echomail out directories and
cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it) then ran mutil mailin again and it tossed everything else that was in my echomail in directory. Started up mystic server and all was good again. So one bad packet mucked up everything.

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

OK so I came home last night and check my board and after I run my bat file for

my interbbs league I notice that it won't connect to the hub saying it
is busy.

So I trying polling FSXNet and it says it is busy. Then I notice that
that mutil starts to run mailin and it says it is waiting for busy
nodes. So I shut down mystic, reboot the computer and same problem. Solution: I deleted all busy semaphores from the echomail out directories and

cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it) then ran mutil mailin again and it tossed everything else that was in my echomail in directory. Started up mystic server and all was good again.
So one bad packet mucked up everything.

I have the very same issue happen to me 3 months ago. You described,
verbatim, a total replay! I was able to resolve using the very same process and have not had the issue since. Crazy.

---

Rocket Town BBS - Telnet: rtbbs.ddns.net
fsxNET: 21:1/203 fidoNET:1:135/383 - sciNET: 77:1/125 Titusville, FL. USA

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Rocket Town BBS (21:1/203)

On 16 Jun 2021, Argos said the following...

OK so I came home last night and check my board and after I run my ba file for

my interbbs league I notice that it won't connect to the hub saying i is busy.

So I trying polling FSXNet and it says it is busy. Then I notice that that mutil starts to run mailin and it says it is waiting for busy nodes. So I shut down mystic, reboot the computer and same problem. Solution: I deleted all busy semaphores from the echomail out directories and

cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it then ran mutil mailin again and it tossed everything else that was in echomail in directory. Started up mystic server and all was good agai So one bad packet mucked up everything.

I have the very same issue happen to me 3 months ago. You described, verbatim, a total replay! I was able to resolve using the very same processand have not had the issue since. Crazy.

This could be solved with just a quick `./fidopoll killbusy` command. =)

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07── |08[|10eml|08] |15ml@erb.pw |07── |08[|10web|08] |15www.erb.pw |07───┐ |07── |08[|09fsx|08] |1521:1/158 |07── |08[|11tqw|08] |151337:1/101 |07┬──┘ |07── |08[|12rtn|08] |1580:774/81 |07─┬ |08[|14fdn|08] |152:250/5 |07───┘
|07── |08[|10ark|08] |1510:104/2 |07─┘

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)

On 15 Jun 2021, Sparky said the following...

my interbbs league I notice that it won't connect to the hub saying it
is busy.

cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it) then ran mutil mailin again and it tossed everything else that was in
my echomail in directory. Started up mystic server and all was good again. So one bad packet mucked up everything.

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Yes that was a problem for me with the 2021/02/12 in Linux as well. There are updates even this month that fixed many of the bad packet hangs. Try updating
if your really using 2021/02/12 (Windows/32) as the tag line shows.

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

On 16 Jun 2021, MeaTLoTioN said the following...

This could be solved with just a quick `./fidopoll killbusy` command. =)

Not quite, ./mis poll killbusy
it shows as A47 and that is the command since A46.

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

This could be solved with just a quick `./fidopoll killbusy` command. =)

Actually no, first I don't use or still have fidopoll (I use mis poll) second the bad packet would just create more .bsy flags next time packets were tossed . (but thanks for the suggestion) Hopefully (as i see someone else had the same
issue) someone else who comes across this problem will be able to find this solution.
Jeff

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Yes that was a problem for me with the 2021/02/12 in Linux as well.
There are updates even this month that fixed many of the bad packet
hangs. Try updating if your really using 2021/02/12 (Windows/32) as the tag line shows.

Thanks for the tip, will update when I get back from vacation next week.
Jeff

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Not quite, ./mis poll killbusy
it shows as A47 and that is the command since A46.

Or in my case mis poll killbusy since I am running under win 32 :)

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Or in my case mis poll killbusy since I am running under win 32 :)

Did you get your version of v47 updated? I noticed you're running an older version from February. The latest version fixed all of those issues for me on linux, however I did not try my windows test box. Curious to know if the new version fixed your polling issues on windows prior to upgrading it, as I'm currently running a stable v47 on windows for my testing system. My RPI is on one of the later (but not the latest) version and it's running great. Prior I had to add a .sh file to mis poll killbusy all, poll each hub individually, with a 10 second delay in between each, and then process my inbound mail. It was a pain but the new MIS seems to work perfectly.

-tG

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Or in my case mis poll killbusy since I am running under win 32 :)

Did you get your version of v47 updated? I noticed you're running an older version from February. The latest version fixed all of those
issues for me on linux, however I did not try my windows test box. Curious to know if the new version fixed your polling issues on windows prior to upgrading it, as I'm currently running a stable v47 on windows for my testing system. My RPI is on one of the later (but not the
latest) version and it's running great. Prior I had to add a .sh file to mis poll killbusy all, poll each hub individually, with a 10 second
delay in between each, and then process my inbound mail. It was a pain but the new MIS seems to work perfectly.

-tG

I updated to the newest, AND I had cr1mson(KANSIT) go over my FTN setup.. he sayes its all ironed out now (Netmail should work on 2o again!) BUT I'm still getting danged poll.bsy files in my /semaphore that holds up my polling of the FTNs.

I *did*, however, STILL have that temppoll.sh running - SO I just turned THAT off and ONLY have the standard ./mis poll forced | ./mutil mailin running now... I'm hoping to see that iron all the bubbles out. I'm over this farting around trying to get things running like they did a couple months ago. :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hello paulie420.

20 Jun 21 17:43, you wrote to The Godfather:

Or in my case mis poll killbusy since I am running under win
32 :)

Did you get your version of v47 updated? I noticed you're
running an older version from February. The latest version fixed
all of those issues for me on linux, however I did not try my
windows test box. Curious to know if the new version fixed your
polling issues on windows prior to upgrading it, as I'm currently
running a stable v47 on windows for my testing system. My RPI is
on one of the later (but not the latest) version and it's running
great. Prior I had to add a .sh file to mis poll killbusy all,
poll each hub individually, with a 10 second delay in between
each, and then process my inbound mail. It was a pain but the
new MIS seems to work perfectly.

-tG

I updated to the newest, AND I had cr1mson(KANSIT) go over my FTN
setup.. he sayes its all ironed out now (Netmail should work on 2o
again!) BUT I'm still getting danged poll.bsy files in my /semaphore
that holds up my polling of the FTNs.

i've tested the netmail and only the fsxnet netmail arrived from your system to mine. but nothing goes back. no fidonet or tqwnet netmails arrived to/from me.
:(

I *did*, however, STILL have that temppoll.sh running - SO I just
turned THAT off and ONLY have the standard ./mis poll forced | ./mutil mailin running now... I'm hoping to see that iron all the bubbles out.
I'm over this farting around trying to get things running like they
did a couple months ago. :P

|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Daniel

... 10:02am up 5 days, 23:02:00, load: 69 processes, 275 threads.
--- GoldED+/EMX 1.1.4.7
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

I updated to the newest, AND I had cr1mson(KANSIT) go over my FTN
setup.. he sayes its all ironed out now (Netmail should work on 2o again!) BUT I'm still getting danged poll.bsy files in my /semaphore
that holds up my polling of the FTNs.
I *did*, however, STILL have that temppoll.sh running - SO I just turned THAT off and ONLY have the standard ./mis poll forced | ./mutil mailin running now... I'm hoping to see that iron all the bubbles out. I'm
over this farting around trying to get things running like they did a couple months ago. :P

Thats so wierd, when I upgraded I didn't have .bsy issues anymore, but also abandoned the temppoll.sh right away ..

lemme know how things work for you as I'd like to upgrade to 6.20 on the RPI, but am hesitent. Like you, I'd rather be drawing ANSI, coding, or changing my menus around to confuse my users (keep them on their feet :) then to be farting around with polling issues out of my control.

-tG

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

i've tested the netmail and only the fsxnet netmail arrived from your system to
mine. but nothing goes back. no fidonet or tqwnet netmails arrived
to/from me. :(

So, I assume I'll need to check my BINK port and... that side of things. Hmmmm.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Thats so wierd, when I upgraded I didn't have .bsy issues anymore, but also abandoned the temppoll.sh right away ..

lemme know how things work for you as I'd like to upgrade to 6.20 on the RPI, but am hesitent. Like you, I'd rather be drawing ANSI, coding, or changing my menus around to confuse my users (keep them on their feet :) then to be farting around with polling issues out of my control.

-tG

Ahhh, now I see what the hub bub is about. Another new build, eh. :P

Maybe I'll just go for it and... couldn't hurt; g00r00 did a great job on the last one. I'm gonna give it a crack.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hello paulie420.

21 Jun 21 09:42, you wrote to me:

i've tested the netmail and only the fsxnet netmail arrived from
your system to mine. but nothing goes back. no fidonet or tqwnet
netmails arrived to/from me. :(

So, I assume I'll need to check my BINK port and... that side of
things. Hmmmm.

i'm not sending crash mails to you, only routed netmail, so if you get echomails, you should get netmails too..

|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Daniel

... 12:07am up 7 days, 1:06:50, load: 69 processes, 275 threads.
--- GoldED+/EMX 1.1.4.7
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

Ahhh, now I see what the hub bub is about. Another new build, eh. :P

Maybe I'll just go for it and... couldn't hurt; g00r00 did a great job
on the last one. I'm gonna give it a crack.

I pulled the trigger and did it, and actually was able to narrow down my problem newly appearing .bsy issues thanks to the improved logging. I had been polling PiNet, but I know he's been manually reentering all of his nodes for retronet, and I'm sure PiNet is also the same case? Anyway, I had been getting "Unauthorized something .." Anyway, I simply set it to Not active, and all of my .bsy issues went away. I am having the same issue with DoreNet and HappyNet. So turning both to Not active has made this new version run even more smoothly then the 6.7 ..

-tG

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

I pulled the trigger and did it, and actually was able to narrow down my problem newly appearing .bsy issues thanks to the improved logging. I
had been polling PiNet, but I know he's been manually reentering all of his nodes for retronet, and I'm sure PiNet is also the same case?
Anyway, I had been getting "Unauthorized something .." Anyway, I simply set it to Not active, and all of my .bsy issues went away. I am having the same issue with DoreNet and HappyNet. So turning both to Not active has made this new version run even more smoothly then the 6.7 ..

-tG

Alright; what are the new logging options that were helpful, tG? I think that I have some FTN issues buried away - EVEN after cr1mson ironed me out a little better than I know how. I deleted SciNet everything, and my system is either still polling SciNet OR SciNet is still polling ME...

But I see SciNet things; so... something is amiss on my end.

Also, my Linux binary app/external programs issue has come back. When I run an external program (Like Lynx or cmatrix for Matrix Rain...) Linux is sending MANY extra * characters to the end user. WHY!?!??!?! OMG. My AFK looks horrible; as does Lynx... and I had fixed this with a Mystic upgrade, but it came back... so now I actually have to FIND the exact reason and iron it out.

OMG - always something.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Did you get your version of v47 updated? I noticed you're running an older version from February. The latest version fixed all of those

Upgraded before I went on vacation for a few days and all seems well. The real culprit was a bad packet and knock on the monitor I haven't had a bad packet since (or if I did I haven't seen evidence of it)
Jeff

--- Mystic BBS v1.12 A47 2021/06/19 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

On 23 Jun 2021, paulie420 said the following...

have some FTN issues buried away - EVEN after cr1mson ironed me out a little better than I know how. I deleted SciNet everything, and my
system is either still polling SciNet OR SciNet is still polling ME...

But I see SciNet things; so... something is amiss on my end.

Did you remove all echos & file areas via AreaFix from SciNet before removing the setup? If not, his system will still try and send them to you.

You can always add bbs.diskshop.ca's IP address (45.72.177.237) to mystic/data/blacklist.txt as well.


Jay

... I'm a soldier, not a diplomat. I can only tell the truth.

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

But I see SciNet things; so... something is amiss on my end.

Did you remove all echos & file areas via AreaFix from SciNet before removing the setup? If not, his system will still try and send them to you.

Ahhh, you know what - I bet I didn't remove the file areas... I know I haven't. :P I'll give that a shot and see whats what.

You can always add bbs.diskshop.ca's IP address (45.72.177.237) to mystic/data/blacklist.txt as well.

True... will think about that, altho its no huge deal. TBH, I wish SciNet was still a viable FTN - I really liked it.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 24 Jun 2021, paulie420 said the following...

True... will think about that, altho its no huge deal. TBH, I wish
SciNet was still a viable FTN - I really liked it.

You're not missing anything as it seems to be down yet again.

It's good when it's working, that's where I was chatting w/ g00r00, but I guess I can do that on Fido as well.


Jay

... Sorrow looks back, worry looks around, faith looks up.

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Upgraded before I went on vacation for a few days and all seems well.
The real culprit was a bad packet and knock on the monitor I haven't
had a bad packet since (or if I did I haven't seen evidence of it)
Jeff

Yeah I haven't had issues either so I'm pretty happy with this upgrade. I went ahead and turned on the taglines for the time being as it's pretty cool; but haven't edited any of my ANSI's to indicate so to the users yet. I also added the OC access flag as a new user ANSI for their first login only. So some neat little nuggets he's adding to v47 .. trying to keep up on them all ... one thing I'm learning is to not simply do ./install replace ~/mystic ... as there are new ansi's and data files being introduced as well.

-tG

... My software never has bugs. It just develops random features...

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Alright; what are the new logging options that were helpful, tG? I think that I

It's been some time since I've read the readme.txt file for that specific bullet point, but I think it was both poll.log and mutil that has more data when things aren't performing right. However if you're looking for the more robust logging to view .. I'll check out ArakNet's Mystic Support where he replied to me with some special logging command that could be performed as well.

have some FTN issues buried away - EVEN after cr1mson ironed me out a little better than I know how. I deleted SciNet everything, and my
system is either still polling SciNet OR SciNet is still polling ME...

You're likely getting stuff from SciNet because he hasn't removed you from the nodelist and so his system is still calling you. I can log on your system and check out polling, if I can find the password you gave me :)

Also, my Linux binary app/external programs issue has come back. When I run an external program (Like Lynx or cmatrix for Matrix Rain...) Linux is sending MANY extra * characters to the end user. WHY!?!??!?! OMG. My AFK looks horrible; as does Lynx... and I had fixed this with a Mystic upgrade, but it came back... so now I actually have to FIND the exact reason and iron it out.

I think ML helped ya with this one, is it all fixed now? It was Screen causing the issue I think you said.

-tG

... A program is used to turn data into error messages.

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Here is the command line logging g00r00 had me do that helped him/I discover a few more issues.

strace -s -o mistrace.txt ./mis poll forced

the rest was just poll.log and mutilXXXXXX.log which either I changed the level of logging or I think it's in whatsnew.txt that he added extended logging to one of them.

-tG

... Top secret! Burn before reading!

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Yeah I haven't had issues either so I'm pretty happy with this upgrade.
I went ahead and turned on the taglines for the time being as it's
pretty cool; but haven't edited any of my ANSI's to indicate so to the users yet. I also added the OC access flag as a new user ANSI for their first login only. So some neat little nuggets he's adding to v47 .. trying to keep up on them all ... one thing I'm learning is to not
simply do ./install replace ~/mystic ... as there are new ansi's and
data files being introduced as well.

-tG

Wait - I still only do ./install replace ~/mystic - am i missing something, tG???

since you know... 05/07 or whatever, thru 06/21????



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

You're likely getting stuff from SciNet because he hasn't removed you
from the nodelist and so his system is still calling you. I can log on your system and check out polling, if I can find the password you gave
me :)

No problem, my sysOp pw is "paulieisTHEis6969". Thanks for the help, man - don't tell anyone that I have no idea what I'm doing... Omg.

I think ML helped ya with this one, is it all fixed now? It was Screen causing the issue I think you said.

-tG

Yup - all 'fixed'. Screen was changing the terminal settings from 256 colors to, I think, 8... and that caused Mystic to return some nasty * characters over all my binary Linux apps that I called from Mystic. Anyway, running ./mis daemon fixed all of it - and with some fancy schmancy cli commands I COULD run screen still and have ./mis server still function correctly. But I'm learning to live with ./mis daemon. :P Oh, the things we learn... don't learn... get thru, and don't get thru. I actually hate all of this and am gonna go 100% facebook soon... :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Here is the command line logging g00r00 had me do that helped him/I discover a few more issues.

strace -s -o mistrace.txt ./mis poll forced

the rest was just poll.log and mutilXXXXXX.log which either I changed
the level of logging or I think it's in whatsnew.txt that he added extended logging to one of them.

-tG

You lost me here - but I'm gonna go type this command in and see what pops out anyway. :P

Whiskey? Nevermind....



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Wait - I still only do ./install replace ~/mystic - am i missing something, tG???

I haven't read the rest of your replies so I should probably not write this but I will anyway lol!

Yes .. I would do a clean install in a temp directory and take a look within scripts, text, and data directories. What I found yesterday but not likely ALL:

1. New commands to input into your message readers .ini file. These do not affect your ANSI, but they do change the pop up ESC menu command choices to add tagline options for users who want to or not use taglines. (I just followed the whats new instructions and copied the str#'s out of this .ini file and into my own, since I have custom ansi file and didn't want my x/y coordinates messed up.
2. taglines.ini to make custom tagline menu ansi as well as other options.
3. taglines.dat is a global database of pre written taglines users can use, while also users can create their own custom taglines (*think Marly :) in their "personal tagline" database. The s255 access level is the only that can delete taglines from the global, but any user can delete from their personal.

I can't remember what else I copied over .. this evening I'm looking at mutil.ini as there appears to be changes to this as well, however I *think* they are just new event commands that can be executed that would read a singular mutil.ini file, and only run the semaphores, etc. that you specifically call them to. But I could be wrong ... I haven't had issues with the new version using as is, and just skim read the whatsnew.txt relating to all of the new ./mis stuff as most of it is for hubs.

Hope this helps.

-tG

... I know a good tagline when I steal one!

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

No problem, my sysOp pw is "paulieisTHEis6969". Thanks for the help, man
- don't tell anyone that I have no idea what I'm doing... Omg.

Haha .. omg.

Yup - all 'fixed'. Screen was changing the terminal settings from 256 colors to, I think, 8... and that caused Mystic to return some nasty * characters over

So weird that that happens every update.

correctly. But I'm learning to live with ./mis daemon. :P Oh, the
things we learn... don't learn... get thru, and don't get thru. I actually hate all of this and am gonna go 100% facebook soon... :P

Hahaha .. just remember, FB gets hacked.

-tG

... Operator, give me the number for 911

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

You lost me here - but I'm gonna go type this command in and see what
pops out anyway. :P
Whiskey? Nevermind....

Cheers!

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Wait - I still only do ./install replace ~/mystic - am i missing something, tG???

1. New commands to input into your message readers .ini file. These do 2. taglines.ini to make custom tagline menu ansi as well as other
3. taglines.dat is a global database of pre written taglines

Yea, I know I've asked you at a few places.. BUT, I figured it out and READ the dang upgrade.txt and whatsnew.txt. :P Thats kinda important - but with so many a47 builds, sometimes you just do what you always do...

I will now be checking that EVERYTIME. I know thru the upgrades that I've missed out on a couple 'new demos' that g00 included... and wonder if there was anything else...

I can't remember what else I copied over .. this evening I'm looking at mutil.ini as there appears to be changes to this as well, however I *think* they are just new event commands that can be executed that would read a singular mutil.ini file, and only run the semaphores, etc.

Yea, I didn't do anything with mutil.ini either... since I had custom .ini's, I made the tagline edits myself to my current msg_editor.ini - which is good because I keep learning more and more about how Mystic works and things that can be done. In a round-about way, theres LOTS of modification possibilities.

... Documentation: The worst part of programming.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Yup - all 'fixed'. Screen was changing the terminal settings from 256 colors to, I think, 8... and that caused Mystic to return some nasty characters over

So weird that that happens every update.

Just in case someone else might read this and have a similar issue... it wasn't because of the Mystic updates. It actually was a cause of my using SCREEN...

I'd started loading ./mis server thru SCREEN so that I could re-attach the MIS 'wfc' screen on any SSH connection that I made to my BBS box. A while ago I'd load ./mis server just on the graphical desktop on my Raspberry Pi OS... if I wanted to see it, I'd either have to go to the Pi with a monitor/keyboard or VNC into it...

So I was using SCREEN instead. What this caused, and can be fixed with commands that set SCREENs terminal color mode, was my Linux external apps that ran thru Mystic either with a (DD) command or called by MPL code where displaying extra ANSI/ASCII characters rendering the application to show garbled to the end user.

Anyway, I'm now running in ./mis daemon mode until I decide how I want to ultimately run the Mystic server. I may just end up loading ./mis daemon in a cronjob at boot... I'm learning to use the logs a lot more and another Linux app called LNAV is really helpful and digging thru data in logs...

Who knows...

... Everyone is entitled to my opinion!



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 28 Jun 2021, paulie420 said the following...

Anyway, I'm now running in ./mis daemon mode until I decide how I want to ultimately run the Mystic server. I may just end up loading ./mis daemon in a cronjob at boot...

That's kind of what I do, I run ./mis daemon in rc.local on bootup. I was playing around with starting it as a service before I went and played with Telegard again. Now I'm back to Mystic...


Jay

... Insufficient facts always invite danger. Spock, stardate 3141.9.

--- Mystic BBS v1.12 A47 2021/06/28 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Anyway, I'm now running in ./mis daemon mode until I decide how I wan ultimately run the Mystic server. I may just end up loading ./mis dae in a cronjob at boot...

That's kind of what I do, I run ./mis daemon in rc.local on bootup. I
was playing around with starting it as a service before I went and
played with Telegard again. Now I'm back to Mystic...

Jay

Theres another way I could do it, in rc.local or... one of the other ones.

I really like the mystic_systemd .service thats out there, but it requires to run as root which doesn't [easily] work with my system. Its REALLY nice, tho, and has safegaurds built in to check for bsy's and make sure mis stays running... I wish I could use it; too many MPLs break from permissions issues while running mis in root.

https://vswitchzero.com/mystic-systemd/

... ASCII stupid question, get a stupid ANSI.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)