On 31 Aug 2019, Bradley D. Thornton said the following...
 
 BD> Should I be creating an account on the system for Mystic to run under or
 BD> install as root?

I read the couple replies after this, and didn't know that Mystic switches to
the owner. BUT, on some installs of Linux, running sudo in a bash script or
something similar to launch on startup can be a little complicated, with my
experience having to pipe the password in plain text. An RPi with Raspbian
will happily let you run sudo without a password in a terminal or bash
script; Mint won't, for example.

What I do is install with sudo, then chown and chmod the Mystic directory
recursively:

chown -R maskreet:maskreet /mystic
chmod -R 755 /mystic

Then just run:

setcap 'cap_net_bind_service=+ep' /mystic/mis

to allow non-su to run on ports lower than 1024 for that particular program,
MIS.

Then you never have to deal with sudo to run Mystic again.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)