w00t w00t! If you've any questions just ask - theres some hidden
variables and modifications an in-the-know sysOp can make to make AFK 'their own'. I'm willing to help you make it even more 'Zip' if desired.

Mine works on local machine, but get an "Error opening terminal: unknown" on remote machines after countdown.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Mine works on local machine, but get an "Error opening terminal: unknown" on remote machines after countdown. I am running Mystic 1.12 a48.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Mine works on local machine, but get an "Error opening terminal: unknown" on remote machines after countdown. I am running Mystic 1.12 a48.

I wrote the RCS AFK mod... its been awhile, tho. :P

Do you have cmatrix installed?? Is it maybe that you don't have $TERM
set to something like ANSI-BBS, xterm-color??

I'd check the system by typing;

echo $TERM

cmatrix is installed, hence it works fines on local machine. echo $TERM results with xterm-256color

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I wrote the RCS AFK mod... its been awhile, tho. :P

Do you have cmatrix installed?? Is it maybe that you don't have $TERM set to something like ANSI-BBS, xterm-color??

cmatrix is installed, hence it works fines on local machine. echo $TERM results with xterm-256color

OK - hmmm. tG - any thoughts here? Its really hard to diagnose systems; hence why Docker has been so damn popular... its hard to know/guess your exact setup - and when it just w0rks on our systems... we don't know where to start.

If you looked at the code, you know that I'm just some schmuck getting something w0rking on MY system; I'm no xqtr... :P

Lets see if anyone else chimes in - sorry??

:P



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

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I wrote the RCS AFK mod... its been awhile, tho. :P

Do you have cmatrix installed?? Is it maybe that you don't have set to something like ANSI-BBS, xterm-color??

cmatrix is installed, hence it works fines on local machine. echo $TE results with xterm-256color

OK - hmmm. tG - any thoughts here? Its really hard to diagnose systems; hence why Docker has been so damn popular... its hard to know/guess your exact setup - and when it just w0rks on our systems... we don't know
where to start.

If you looked at the code, you know that I'm just some schmuck getting something w0rking on MY system; I'm no xqtr... :P

Lets see if anyone else chimes in - sorry??

:P

Ok, I've got good news!! Finally got it working remotely. Learned something new in the process of fixing it. Where to start....

I tried your rcsafk mpl with unimatrix instead of cmatrix to see if it would work. It did the same exact thing as cmatrix did, but this time it left me with way more error information. It was complaing about ncurses terminal not set. I do indeed have the term set if I type echo $TERM it shows its set. I did some digging in some forums and learned that a daemon service does not load the term environment for that particular service (i.e. mis). Therefore I believe yours works because you are not executing the BBS service via systemd, but through a terminal instead. I had to go back into mis.service and add a line defining the term environment. Code below...

[Service]
Environment=TERM="xterm-256color"

Also a FYI, Raspberry PI OS doesn't come preinstalled with xterm. So in order to get the afk mod working you will have to install xterm and then add term to the environment if using systemd.

I feel better now... Now to fix another problematic mod, argh!
Cheers!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Do you have cmatrix installed?? Is it maybe that you don't set to something like ANSI-BBS, xterm-color??

Ok, I've got good news!! Finally got it working remotely. Learned something new in the process of fixing it. Where to start....

I do indeed have the term set if I type echo $TERM it shows its set. I fr> did some digging in some forums and learned that a daemon service does fr> not load the term environment for that particular service (i.e. mis). fr> Therefore I believe yours works because you are not executing the BBS fr> service via systemd, but through a terminal instead.

Yep... did you write your mis.service, or is it that one release thats out there?? I don't use the mis.service - but it is a really nice setup!



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

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Yep... did you write your mis.service, or is it that one release thats
out there?? I don't use the mis.service - but it is a really nice setup!

I believe i am using the one thats out there. I tried the prewritten service for MRC but it didn't work so i wrote my own for that one. Not sure if user is suppose to be root or not for that one. it only works for a minute then times out.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)