Hi Jakob On Tue, Oct 21, 2008 at 12:27:11AM +0200, Jakob Lell wrote: > 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.
Now I understand more. However I still have some doubts, see below. > 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. What virtualisation technique do you use? I ask because normally the socket is local to the virtual machine in question. This means that you can not share the socket over the virtual machine border. > 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. Have you run socat on the virtual machine with the virtual machine with vnc client or on the server? As sockets are not easy to share I would like to know. Best regards, // Ola > Jakob > -- --- Inguza Technology AB --- MSc in Information Technology ---- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
