So... I created some systemctl services for running Mystic and MRC Chat
Which I just don't understand because - if I'm running as sudo, and the owner of the file is 'pi', doesn't sudo trump that?? Anyway... I just
In general, when one runs applications as services with systemd, one shouldn't need to use sudo at all.
If the [Service] section of the mis.service file has User=pi and
Group=pi (I guess the "pi" user has a group of its own, too?) in it then everything should execute as the "pi" user and "pi" group. The question
is if that is enough.
Are you running MIS as "root" now (when you start it manually)?
Yea Zip... I thought it was weird that it asked for sudo, too... but the accompanying scripts that go along with mis.service are pretty fancy and allow for Mystic restarting if it hits any issues, and correct shutdown
/ semaphore deleting and... anyway, it looked pretty nice to me so - I'm gonna list all three files, below. First is mis.service, 2nd is mis-start.sh, 3rd is mis-stop.sh...
Hmm, I couldn't locate the sudo part in there, instead it appears to run everything as root?
What error message do you get when using the systemd service?
(journalctl -u mis)
And does anything appear in the MIS logs?
You might want to try adding -x to the first line in the scripts to get "all" output from them:
...and then perhaps it makes it easier to locate the point where you get some permission error message (e.g. using journalctl -u mis)?
|Location:||Riverside County, California|
|Nodes:||15 (0 / 15)|