Hi Ola,
the main reason why I want to use unix domain sockets is that I
sometimes run a lot of virtual machines with kvm simultaneously.
Normally I only access the machines via ssh. However, I have to use vnc
to debug problems with the network configuration. So I just use vnc as a
convenient way of accessing the display, keyboard and mouse of virtual
machines on a local system when needed.
As I use scripts for starting the virtual machines, it is a bit
problematic to allocate a unique display number for every machine
automatically. Another advantage of unix domain sockets is the simple
and effective access control which can even prevent (possibly untrusted)
local users from connecting to it. This isn't possible with tcp ports.
So it's not even necessary to use a vnc password.
Kvm already supports unix domain sockets for its vnc server. However,
the only way I've found to use this is redirecting the vnc data stream
using a program like socat.
Jakob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
