I'm posting this here as I think its more a Linux issue than a Mystic one. Maybe it would live better in a Mystic area, but... this is what I chose.

ISSUE: I noticed my Linux binary apps running as an external command thru Mystic were displaying MANY * characters (Not actual astericks, but an ANSI character that looks like one...) and rendering then unviewable to the end user.

Such as Lynx, for gopher browsing, cmatrix, which I use as a screensaver and other Linux binaries I call with a Mystic (DD) command.

What I found out, with help from [who else] MeaTLoTioN, is that the issue came up AFTER I started loading './mis server' thru screen. I would load screen, run './mis server' and then detach the screen... this way I could reattach screen from any system thru SSH and see the Mystic server menu.

Anyway, I shut Mystic server down and just ran './mis daemon' and viola, no more extra characters in my Linux binary apps...

So now I'm testing and trying to learn WHY and ... I do like to have the Mystic server screen available to view; but not at the cost of issues with external apps that my BBS needs to run.

So - I'll update as I learn the WHY... do you have any ideas? I'm LEARNING that I can run MIS in daemon mode and find all the data I might need thru the logs - I'm learning to use LNAV to find anything in those logs quickly... but that IS new to me, so...

Was thinking maybe I'd have better luck with tmux... or, maybe screen ISN'T running in xterm 256 color mode or... something; so I might be able to learn the WHY and fix it while still using screen - but... this is where I'm at today. At least I was able to FIX the issue... but I'm a little lost w/o the Mystic server screen.... really, why?? I just use it to look over my events; which I can do in the logs.. so. Hmmmm. I'm fine; but I always strive to KNOW the whys and understand things.

Ok, I'll stop. :P Any thoughts or input is welcome.



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

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

So now I'm testing and trying to learn WHY and ... I do like to have the Mysticserver screen available to view; but not at the cost of issues
with externalapps that my BBS needs to run.

Here's why;

without screen;

$ echo $TERM
xterm-256color

with screen;

$ echo $TERM
screen.xterm-256color


Possible solution (from inside screen);

$ TERM=xterm-256color && ./mis server

Untested, but should work (maybe?)

My opinion;

Don't use screen, use daemon instead, and learn using the log files to your advantage, you get more info out of them.

Good luck, hope this helps.

---
|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 (1337:1/101)

Am 27.06.21 schrieb MeaTLoTioN@1337:1/101 in TQW_LINUX:

Hallo Meatlotion,

Here's why;
without screen;
$ echo $TERM
xterm-256color
with screen;
$ echo $TERM
screen.xterm-256color

Possible solution (from inside screen);

$ TERM=xterm-256color && ./mis server

Untested, but should work (maybe?)

I thought about something like this, too.

Considering your command:
I would prefer either
$ export TERM=xterm-256color && ./mis server
or
$ TERM=xterm-256color ./mis server

I don't know instantly if in your solution the variable will be kept for
the part after &&, hence my "export" idea.
Without using &&, the TERM variable will be set for the ./mis process.

Don't use screen, use daemon instead, and learn using the log files to
your advantage, you get more info out of them.

Isn't there "nodespy" or something like this in Mystic which should give
you some insight into your running BBS?

Regards,
Anna

--- OpenXP 5.0.50
* Origin: Imzadi Box Point (1337:1/108.1)

So now I'm testing and trying to learn WHY and ... I do like to have

Here's why;

without screen;

$ echo $TERM
xterm-256color

with screen;

$ echo $TERM
screen.xterm-256color

Possible solution (from inside screen);

$ TERM=xterm-256color && ./mis server

Untested, but should work (maybe?)

My opinion;

Don't use screen, use daemon instead, and learn using the log files to your advantage, you get more info out of them.

Good luck, hope this helps.

GRRRRRRRR, but so NOT grrrrrr too. :P I was gonna take some time to test and figure out why - and you always swoop in and drop the answers on me. :P Which I hope you continue to do when you have knowledge that can help me... I can still go in and test, now, and ultimately grasp things more quickly. I thank you...

And, I know yer right - I was testing some python software that displays all the colors of the terminal. (x84 BBS softwares ct-color scan demo...) When running under screen it only showed 8 colors; and now without screen it is in 256 color mode.

At any rate, I'm learning how the terminal can affect the things you have, lol, running in it. :P (Duh...) Anyway, yes - your post is helpful and appreciated.



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

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

I don't know instantly if in your solution the variable will be kept for the part after &&, hence my "export" idea.
Without using &&, the TERM variable will be set for the ./mis process.

Thanks for your extra details about settings for screen. I am understanding things a lot better now and see how my settings were messing up my external programs being ran.

Isn't there "nodespy" or something like this in Mystic which should give you some insight into your running BBS?

There is a nodespy... the mis 'WFC' screen shows event history and node information... I'm quickly learning that some other apps, like lnav log viewer, are really helpful in seeing even MORE data than is shown in mis. Its different, but if I get used to it... the data is just listed a bit differently. I'll be just fine. :P

And, I can choose to LEARN how screen works and still utilize it if I want. I think I'll prolly add ./mis daemon to a cronjob or otherwise load it at boot..



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

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