> On Oct 9, 2022, at 07:35, Rob Landry <[email protected]> wrote:
>
> I've had my share of difficulties running Xvnc on Rivendell systems lately.
> The VNC service will crash; or it will stop responding to mouse clicks or
> keystrokes; and in some cases even the keyboard and mouse attached to the
> physical machine will become unusable.
>
> Some machines never experience problems; others experience them frequently.
> In some cases, killing and restarting Xvnc will resolve the problems, but in
> others, I have to reboot the machine.
>
> The problem has been encountered on machines running CentOS 7, with Rivendell
> installed via the Paravel install script. I've encountered the problem with
> both Rivendell V2 and Rivendell V3. I don't remember seeing the problem on my
> older Debian-based Rivendell machies.
>
> Has anyone else but me encountered this sort of problem?
Never anything of that intensity (where it affects the local X server), but I
haven’t run Xvnc in ages. You might want to try out our x11vnc-based setup,
which uses Systemd socket-activation to start up an x11vnc session on demand.
To get it, do:
On RedHat-ish setups: sudo yum install x11vnc-auto
On Ubuntu-ish setups: sudo apt install x11vnc-auto
After installing, then set it up:
sudo systemctl start x11vnc-auto.socket
sudo systemctl enable x11vnc-auto.socket
vncpasswd
N.B. - no ’sudo’ on the last command!
Cheers!
|---------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|---------------------------------------------------------------------|
| A room without books is like a body without a soul. |
| |
| -- Cicero |
|---------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
