More > JRiver Media Center 23 for Linux

Systemd services to autostart JRiver and a VNC server

<< < (2/3) > >>

tombert:

--- Quote from: mwillems on September 14, 2017, 04:50:57 pm ---Additionally the always auto-restart should be bringing MC up shortly if it doesn't succeed in loading the first time (unless you changed it to "on failure" as you described, because systemd doesn't always do a good job of distinguishing failure-based shutdowns)

I initially tried that, but my experience was that some of MC's failure modes do not successfully hook "on-failure", so I'd get crashes where MC would never respawn.  I was using this primarily on headless systems, so "always" was a safer choice.  If you want to stop MC on a system with the "always" option, there's always "systemctl stop jriver.service"

--- End quote ---

Ah! that's the reason why you had "always" in the restart option. I am somewhat too lazy to type "systemctl ..." stopping MC.
On the other hand it does not feel like a final solution if I assume it always starts 10 seconds later ...

tombert:

--- Quote from: mwillems on September 14, 2017, 04:50:57 pm ---... but if you are there is something peculiar about your install.

--- End quote ---
Of course it's always the fault of the others  :P

mwillems:

--- Quote from: tombert on September 14, 2017, 05:35:23 pm ---Of course it's always the fault of the others  :P

--- End quote ---

To be clear, I'm not employed by JRiver, I'm just a user like you.   A systemd symlink to a service should be 100% identical to the service pointed to, and if it's not then something very strange is happening (at the systemd or POSIX level, not at the jriver level).

tombert:

--- Quote from: mwillems on September 14, 2017, 06:06:52 pm ---To be clear, I'm not employed by JRiver, I'm just a user like you.   A systemd symlink to a service should be 100% identical to the service pointed to, and if it's not then something very strange is happening (at the systemd or POSIX level, not at the jriver level).

--- End quote ---
Of course you'r right. I just wondered because doing a systemctl list-dependencies shows lightdm and not display-manager.
The reason why it now works better on my server could be the missing gravity of the sun here in Vienna (at time of writing) or simply because systemd is not bug free.
And, don't we know it all better ... how often have you already said ".... it should ..." regarding SW systems!?

Wybe:
I did a clean install of Debian Stretch 9.3 and it appears that jriver.service does not start anymore. Any ideas?

Navigation

[0] Message Index

[#] Next page

[*] Previous page