Consoleaccess

Console access

ToMaTo offers access to the local console of running devices via VNC. VNC can forward the remote graphics output from the device and local keyboard and mouse input to the devices, some VNC clients even offer clipboard access.

Web client

ToMaTo features an integrated VNC client that can be opened from the GraphicalEditor on the control panels of the devices. This VNC client is implemented as a Java applet and requires that a Java plugin is installed and enabled in the browser. You can check if your browser has Java enabled via this link. Depending on your browser and its security settings a security dialog might pop up that has to be accepted before the Java applet is started. Since the Java applet is hosted by all ToMaTo host this dialog might appear multiple times for different devices.

VNC clients

Since VNC is an open protocol any VNC client can bu used to access the console. The needed connection details and login credentials can be viewed in the GraphicalEditor on the control panel of the device.

RFB automation

The protocol of VNC is called RFB and is very simple. There are lots of implementations of RFB that normally only consist of a few hundred lines of code. RFB can be used to send keyboard input to devices and thus automate certain processes.

OpenVZ console

Since OpenVZ virtual machines do not have a dedicated console, a new shell is created and offered as console for each VNC connection. The shell is destroyed shortly after the VNC connection is terminated, i.e. when the VNC client is closed. All processes that are started in the console and are still attached to it when it is destroyed will be terminated. To circumvent this, processes must be detached from the shell. The easiest way to do so is the screen command which should be installed on all templates.