CSE Student Servers

The following servers are available for CSE students to access remotely in order to complete coursework in CSE classes. This allows students to work from home, the library, or elsewhere, while remaining logged in for extended periods of time.

You may connect to any of these machines using ssh from the campus wired and wireless networks, using your ND username and password:

student00.cse.nd.edu
student01.cse.nd.edu
student02.cse.nd.edu
student03.cse.nd.edu

Acceptable Use

These machines should be used for:
  • editing, building, and testing programming assignments for CSE classes, especially those that use multiple cores.
  • creating and grading programming assignments for CSE classes.
  • individual research and exploration, provided this does not interfere with the above.
  • These machines may not be used for:
  • long running CPU-intensive programs, which should be submitted to Condor or the CRC instead.
  • any program that consumes exessive memory, disk, network or interferes with other users of the system.
  • sponsored research, which should be carried out on machines designated for that purpose.
  • anything that violates the law, the CSE honor code, the ND honor code, or OIT Policies.
  • Programs that violate these guidelines may be terminated without notice, with an explanation given to the responsible user. Gross violations may result in banning the user from the system.

    If you are unable to use a machine due to interference from another program, please contact suggest@cse.nd.edu with the name of the machine and any relevant information.

    Access Policy

    The following people may log into the student machines:
  • Undergraduate computer science and computer engineering majors.
  • Non-majors enrolled in a CSE class.
  • CSE graduate students.
  • CSE faculty.
  • Access lists will be updated at the beginning of each semester. If you think you should have access, but do not, please email suggest@cse.nd.edu.

    Advice on Performance

    Because each machine is shared among multiple people simultaneously, users should expect some variations in performance of programs from run to run. If measuring runtime is an important part of your assignment, discuss with your professor how to deal with variations, perhaps by measuring multiple runs and taking the best or average time.

    To allow for uninterrupted performance experiments, faculty may reserve student02 or student03 for use by only students in their class for up to one week at a time. To reserve, please contact suggest@cse.nd.edu at least one week before the desired date.

    The unused cycles on each machine will be harnessed by the Condor distributed batch system. You may briefly see processes named condor_exec.exe, but these should be automatically removed as users log in. You may evict all Condor jobs from a machine by running condor_vacate -fast.

    Technical Info

    Vital statistics of each machine are:
    HP Model DL165 G6
    2 x AMD Model 2431 6-core CPUs
    12 GB RAM
    160 GB SATA Disk
    Gigabit Ethernet
    Red Hat Enterprise Linux 5
    
    To see what processes are currently active, run the top command. Note that this machine has 12 cores, so a load average of 6 would mean that only 6 out of 12 cores are in use.