Last modified: Aug 16, 2019
- Please connect with us on Twitter @RutgersLCSR for up-to-date announcements
- If you are new to CS Resources, see Beginners info
- For users who are have issues with logging in or access, please go to Core 211 between 10:30a-5pm to resolve your issues. If you use it, please bring your laptop
- For students learning to program with fork, see Preventing Fork Bomb on Linux
- Attention CS416 students. Please be aware that fuse mount point must be set in /tmp/ or /freespace/local/ or your program will hang. The reason: root has no access to home dir and fuse is run by root.
- Please be aware that iLab machines have a new CPU Limit policy enforced limitation to prevent abuse and runaway processes.
- Dropbox is not supported as of Oct 15 2018. Use Scarletmail Google Drive. You have unlimited space there instead of 2GB from Dropbox.
- If you have issue connecting to CS machines, make sure to check if your IP is blocked and how to get around the block.
- Starting Fall 2018, all users should be using a machine named: ilab.cs.rutgers.edu which will randomly pick ilab1.cs, ilab2.cs or ilab3.cs. See iLab Machine Status to find status of all iLab servers and iLab desktop machines.
- If you are using python, please follow Using Python on CS Linux machines instruction or many modules wont load properly.
- If you are doing big data with Hadoop, Please see CS Hadoop Cluster information page.
- If you need more space, store them in/common/users/your_netid where have 100GB disk space. See Storage and Technology Options for more info. (July 30, 2018)
- For those users who use emacs on x2go, please use: emacs-23.1 to avoid compatibility issue.
- There are reports that some people have Keyring issue. Try to use your NetID password to unlock it. If you continue to have problem, follow this QuickFix to Gnome Keyring Password instruction.
Finding a Computer to Use
- We recommend remote users to use machine named: ilab.cs.rutgers.edu which will randomly pick ilab1.cs, ilab2.cs or ilab3.cs. If you prefer other machines, please look at the iLab machines status to find the best iLab machines to use.
- If you have issue with specific iLab machine, report it to firstname.lastname@example.org, check Status of iLab Machines and pick a different machine.
- Trouble logging in?
- Have you Created or activated your account?
- Have you Set your CS Password and use it to login?
- There are many available machines you can access locally and remotely. Unless there are specific features you need, example: class virtual machine or CUDA chips, they are essentially the same. Try find machines with less Users and lower Load for better speed.
- Check Current Status of CS Resources in case we have bigger issues.
- Guide on setting your java version
Using iLab Machines
To use CS iLab Machines, we recommend:
- Login in person on a machine located in the Hill Labs (Hill 120, Hill 248, or Hill 252)
- Use Remote Graphical Display, using X2Go client. See instructions on how to do this.
- Use Remote Graphical Display using Microsoft Remote Desktop client.
- An SSH client for a remote command line interface like Putty, Secure Shell aka WinSSH
- A local X-Server (such as Xming or Cygwin on Windows or XQuarts on MacOSX ) and remotely X-Tunnel graphical applications using an SSH client
- If you have issue with specific machine, please check Status of iLab machines.
Home Pages for Students
- You can setup iLab home pages. This homepage needs to be stored in world readable public_html folder (~netid/public_html) and is accessible via http:// www.ilab.rutgers.edu/~your_netid/
1. If you have issues with any CS computing resources
- Can’t login? Set or Reset your CS password or Activate account at https://services.cs.rutgers.edu/accounts
- Check Status of iLab Machines if you can’t access specific machine.
- Check CS Networking and Resource Status if you are having uptime issue.
- Visit iLab Assistant on duty at Hilll 252 (the CAVE) for programming or other questions.
- Visit LCSR Operator at CoRE 235 for account/printing/network etc issues.
- Visit LCSR technical support Staff CoRE second floor for any technical questions you have
- Send email to: email@example.com to a create a support ticket if you prefer email. We will try to get back to you within 2 business days.
2. If you have issues with Non CS computing resources