Subj : mis2
To   : Matt Bedynek
From : Robert Wolfe
Date : Sun Oct 08 2017 10:33:06

->  TL> I always start and stop as the superuser.

-> I haven't tested this but since I dont see a configurable option to fork to
-> unprivleged user that this means always running as root.  In the "industry"
-> this is viewed as not good.  What I do is configure my instances to listen o
-> non-privleged ports (i.e. 2222) then forward 22 to that.

To work around this, I grant the mystic user (the user I use for Mystic)
sudo privs in /etc/sudoers and then while logged in as the mystic user
issue the 'sudo ./mis2' command.  That way all files are written and
owned by the mystic user without having to use the root user to start
and stop the process.
--- Platinum Xpress/Win/WINServer v3.0pr5
 * Origin: Neptune's Lair - Olive Branch MS - winserver.org (1:116/17)

.