Drew,
You are correct. That is exactly how I have it setup, except that
x11vnc and vncserver are both run as systemd services, they aren't
loaded via the autostart folder.
X11vnc will almost never be used, and if so basically only by me and
only if there is a problem and I'm not there.
vncserver/client will be used by station staff for log maintenance,
etc. I have only configured only one virtual display for this purpose.
I know I can create more, but as you noted, the more sessions, the more
the main machine gets bogged down. Also, I would rather the staff work
around each other rather than everyone doing separate things
simultaneously. I know that creates a bit of inconvenience, but its
still a monumental leap forward to what we have now. With what we have,
you have to do EVERYTHING intrusively on the main playout screen.
For what its worth, although I am a ripe candidate for multiple RD
systems with a central database, I am not going that route right now. I
am still so new at this my plan will be to roll several 'stand-alone'
workstations out in the coming year. This is how our systems are
currently set up as well.
As I gain confidence/experience I will revisit the client/server
model of RD in the future.
By the way, my question still hasn't been answered yet: Since I have
created a new linux user for the purpose of having a virtual desktop to
log into, are there any user groups this user needs to be added to or
any permissions issues I need to be aware of? Again, in my limited
testing the answer seems to be 'no", but I'd like to double check just
in case.
Thanks,
-Alan
On 11/17/2018 5:34 AM, drew Roberts wrote:
Great...
On Thu, Nov 15, 2018 at 3:28 PM Alan Smith <[email protected]
<mailto:[email protected]>> wrote:
I've sorted it out.
Just leaving notes here for anyone that may benefit:
The root cause was trying to create a display for user 'rd' to vnc
into. Since rd will be logged into a local account with a real
display
that caused all sorts of issues for me:
snip
So basically I needed the local account ('rd' with the appliance) as
normal, but a *separate* linux user account that can be vnc'd into
for
the virtual stuff. So I created a 'vncuser' account, set that up to
load up as a systemd service, and it appears to work.
Only thing I am worried about is this new 'vncuser' having the
correct
permissions to edit clocks, logs, etc. So far it looks like its
working
fine with no ill effects.
Sounds about right. If you set up x11vnc on the same box to start from
a .desktop file in ~/.config/autostart, you can vnc to that to see
what is happening in the actual onair studio (for instance) or to
pretend you are there when no jock is present. Then the vncserver /
vncuser combo will give other users the ability to log in to that
machine and have their own desktop. If I understand correctly how you
have that one set up.
I would watch carefully to make sure the vnc users don't bog down the
machine to the detriment of the onair studio. Before I was involved
with Rivendell on a professional level, I once set up a linux machine
that allowed multiple different users to log on at the same time via
vnc so that jocks could check their email and other things without
having to run those apps on a windows based onair machine.
-Alan
all the best,
drew
--
Enjoy great *Bahamian Music* at:
Bahamian Or Nuttin - http://www.bahamianornuttin.com
<http://www.bahamianornuttin.com/>
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
