INTERACT FORUM
More => Old Versions => JRiver Media Center 27 for Linux => Topic started by: Mike Noe on February 20, 2021, 07:37:25 am
-
This might be expected behavior -- not sure.
I have a systemd (--user) unit script [Unit]
Description=JRiver
After=display-manager.service
[Service]
Type=simple
Environment=DISPLAY=:0
ExecStart=/usr/bin/mc27 /MediaServer
Restart=always
RestartSec=10
KillSignal=SIGHUP
TimeoutStopSec=45
LimitRTPRIO=100
[Install]
WantedBy=graphical.target
systemctl --user start jriver.service works fine, journalctl reports success, but mediacenter never starts. I'm assuming because it's a "stub"?
Of course, setting ExecStart=mediacenter27 works fine.
-
the ExecStart line should read
ExecStart=/usr/bin/mediacenter27 /MediaServer
not MC27
I see you also don't have the line:
User=your_user_here, which is in the instructions from mwilliams in his post from15 Jan 2020
https://yabb.jriver.com/interact/index.php/topic,123771.msg857001.html#msg857001
-
the ExecStart line should read
ExecStart=/usr/bin/mediacenter27 /MediaServer
not MC27
I see you also don't have the line:
User=your_user_here, which is in the instructions from mwilliams in his post from15 Jan 2020
https://yabb.jriver.com/interact/index.php/topic,123771.msg857001.html#msg857001
I think he's running the service as his user rather than as a systemwide service so he might not need the user entry.
Interestingly, if I run the new mc27 stub with no flags, it starts MC just fine, but adding the /MediaServer flag just returns success without starting MC. So it's something about the flag that's confusing it I think.
-
Interestingly, if I run the new mc27 stub with no flags, it starts MC just fine, but adding the /MediaServer flag just returns success without starting MC. So it's something about the flag that's confusing it I think.
Could just be running Media Server.