I saw a message earlier about someone wanting to start mystic at boot. I've tried a few things, like it was posted, they were all for older versions of mystic, can someone post how they do it under ubuntu/64 bit?

Thanks

--- Mystic BBS v1.12 A39 2018/02/28 (Linux/64)
* Origin: New Frontier 2| thenewfrontier2.hopto.org (Ohio) (21:2/105)

On 04/02/18, KrUpTiOn said the following...

I saw a message earlier about someone wanting to start mystic at boot. I've tried a few things, like it was posted, they were all for older versions of mystic, can someone post how they do it under ubuntu/64 bit?

I run a short script from the start of /etc/rc.local:
/usr/local/bin/check-mystic

# clean exit
exit 0 ------------------------------------------------------------------------------ #!/bin/bash
# check-mystic
MYSTIC="/mystic" #Path to mystic
MIS_OPTS="DAEMON"
PID='/bin/pidof mis'
if [ "$PID" = "" ]; then
cd $MYSTIC
rm -f semaphore/mis.bsy
./mis $MIS_OPTS
fi ----------------------------------------------------------------------------- So the script above checks for mystic running (checks it's pid really), then clears any junk flags in semaphore from last run and starts it. You could
run it all under rc.local, but I was already using an older script like this and just adapted it rather than changing /etc/rc.local at all. That one is running under Ubuntu 14.04 LTS, has been tested with Ubuntu 16.04 LTS and should run under any Ubuntu (32bit or 64bit). I have tested it with a 32bit Ubuntu 16.04 LTS as well, just no other versions. I also run the same version on the Pi under Raspbian.

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 04/09/18, Vorlon said the following...

Correction on the data line:

stty rows 25 cols 80 && dosemu -I"serial { com 1 virtual 1 }"

Missed a } on the end. #-)

Thank you SOOOO much! that worked perfectly!

--- Mystic BBS v1.12 A39 2018/04/08 (Linux/64)
* Origin: New Frontier 2| thenewfrontier2.hopto.org (Ohio) (21:2/105)