From CS552 Course Wiki: Spring 2017

Main: Using Mentor remotely

You must use the Computer Science linux computers to do your work for 552. In the past, students who have used the CAE systems have experienced difficulty. The instructions and procedures given will not work as intended.

There are many ways to use the CS machines remotely (i.e. from your home, CAE lab, or some place else). Some connections are persistent, while others are not.

NOTE: All mumble machines are rebooted on Monday mornings. So expect persistent connections to be disconnected.

Method 1: ssh (Fastest method)(Non-persistent connection)

If you wish to use the CS systems remotely, either from home or from CAE workstations, you may log on with the command:

ssh -X

where "username" is your CS login name, and "system" is replaced by the name of the individual computer (e.g. mumble-01).

When you log in, you will be asked for your password. Once you type it in, the window you are running is a window into your CS account. Other programs that you open up from that window will access your CS afs directory. You can run dmgr, da, and most anything else you might need in this way. Use "ps -lA" to see if you happen to be using a system already loaded down by an in-person user.

To run mentor over an ssh connection, you must have the mentor fonts set up on the machine that you are logging in from. Instructions for doing this vary from system to system. Only some systems have had instructions identified for them. If you are having problems with fonts or get a font error, read the Tools FAQ.

Method 2: Remote desktop connection (Persistent connection)

If you are familiar with Windows Remote desktop protocol, you can use that. Email for help.

Method 3: Connect using load balanced vncs (Non-persistent connection)

Method 4: Setup your own vnc and connect to it (Persistent connection)

Part I: Setting up the server (To be done only once)

% vncpasswd

% stashticket

% runauth /usr/bin/vncserver -geometry 1280x1024

The vncpasswd command will ask you for a password - type in a password here. This should NOT be your CS password, this is a new password you must create. Also you can pick the resolution that suits you best.

Part II: Connecting to server remotely

Instructions from CSL are here

Part III: Killing a vnc server (To be performed once when you are done using the vnc)

To keep track of your active vnc sessions, you can check the .pid files in <home folder>/.vnc.

To kill a vnc session on, Login to mumble-07 and type the following command

% vncserver -kill :1

Retrieved from
Page last modified on February 03, 2016, at 11:11 AM