INTERACT FORUM

More => Old Versions => JRiver Media Center 24 for Linux => Topic started by: biblio on February 20, 2019, 11:09:31 pm

Title: run panel/medianetwork without UI?
Post by: biblio on February 20, 2019, 11:09:31 pm
I ended up installing gnome on my file server so i could run MC directly from the source but i'd like to not do that if possible.

The file server just runs for gizmo/panel access so i don't need anything visual now that i've set it up.
Title: Re: run panel/medianetwork without UI?
Post by: JimH on February 21, 2019, 06:39:14 am
Yes, you can run MC without a UI on one machine and use any JRiver remote to access it.
Title: Re: run panel/medianetwork without UI?
Post by: BryanC on February 21, 2019, 09:03:58 am
You will still need a dummy X server running, but it's not necessary to run a huge DE like GNOME. I personally use Openbox on my headless server but you can also configure tigerVNC to start one or just run a very lightweight DE like LXQT or XFCE.
Title: Re: run panel/medianetwork without UI?
Post by: biblio on February 21, 2019, 10:29:15 pm
Openbox is good if i have to keep x running.
if those tools could be separated into a daemon or background service it would be better but it's not the end of the world.

I think i'll just keep gdm3 and have my session default to an empty openbox.
Title: Re: run panel/medianetwork without UI?
Post by: blgentry on February 26, 2019, 03:27:23 pm
It's still pretty useful to be able to get to the MC GUI, even on a headless server.  My Raspberry Pi has not been hooked up to a monitor in a very long time; even through OS reinstalls and MC reinstalls.  But I run MC in a VNC session which auto starts (and auto restarts).

Every few months, I find myself needing to see the MC gui for various reasons and having it there via VNC makes it easy.  If my Raspberry Pi can do it with minimal resources, a real computer should have no problems I would think.

Brian.
Title: Re: run panel/medianetwork without UI?
Post by: Awesome Donkey on February 26, 2019, 03:51:48 pm
I do the same thing Brian does, and it works pretty well. I usually remote into it when making library changes and/or weekly for Pi updates and maintenance.