Subj : Re: screen & Mystic issues: UPDATE
To   : acn
From : paulie420
Date : Sun Jun 27 2021 11:38:52

 ac> I don't know instantly if in your solution the variable will be kept for
 ac> the part after &&, hence my "export" idea.
 ac> 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.

 ac> Isn't there "nodespy" or something like this in Mystic which should give
 ac> 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)

.