DOS PROJECT2 - COP5615 Distributed Operating Systems Fall...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
COP5615 Distributed Operating Systems Fall 2011 Computer and Information Science and Engineering University of Florida Project 2 Office: CSE E309 in office hours Due[Campus]: Oct 24th 2011 local 23:55 pm TA : Kun Li ([email protected]) Due[EDGE]: Oct 28th 2011 edge 23:55 pm In project 2 our main goal is to familiarize you with multithreaded programming. Resources: Sun Microsystems Guide to Sockets: http://download.oracle.com/javase/tutorial/networking/sockets/ Note on Runaway Processes: Your threads should terminate gracefully. While testing your programs run-away processes might exist. However these should be killed frequently. Since the department has a policy on this matter, your access to the department machines might be restricted if you do not clean up these processes. To check your processes running on a Unix: ps -u <your-username> To kill all Java processes easily in Unix, type: skill java To check runaway processes on remote hosts: ssh <host-name> ps -u <your-username> And to clean: ssh <host-name> skill java Grading Guidelines: Coding Style (comments, indentations) 10% Clean Termination (runaway processes) 10% Correct Implementation 70% Report and User Documentation 10% For the first three projects, the primary TA who is responsible for creating the project will perform grading. But regardless of who grades the project, the TAs will follow the general guidelines for grading given above. Late Submission Policy: Late submissions are not encouraged but we rather have you submit a working version than submit a version that is broken or worse not submit at all. Every late submission will be penalized 10% for each day late for up to a maximum of 5 days from the due date. Guidelines for Project Report: In addition to submitting any relevant user documentation that will help a third person to compile your code and execute it, we require that you submit a one-page report. Your report file must be named report.txt. Since we will use a UNIX environment during grading phase, we recommend you use a UNIX friendly text editor (gedit, nano, pico, vi, etc.). Your report file should contain details on what you learned from this project, what challenges you faced, how you overcame those, and any other observation, improvements, or interesting facts you might want to pass on to the instructor and the TA. CISE Systems Help and Related Issues: The TA for this class is not responsible for managing CISE department’s computing facilities. So if you run into any access problems with your account or if you find some remote
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
machine unresponsive while implementing your project, your best bet will be to contact the CISE admin people directly at [email protected] Do NOT email the Tas regarding such issues, the Tas already receive tons of emails. Help your Tas fight insanity First semester EDGE students may not have created a valid CISE account yet. They should contact the CISE administrators for account creation. Without a valid CISE account you cannot log on to CISE machines. http://www.cise.ufl.edu/help/ has all the
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/18/2012 for the course COP 5615 taught by Professor Staff during the Fall '08 term at University of Florida.

Page1 / 9

DOS PROJECT2 - COP5615 Distributed Operating Systems Fall...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online