Programming Project #1 Forking Processes

1. Programming Project #1Forking Processes Due Thursday, January 24, 6:00 PM Introduction

2. Programming Assignment • Write a command called doit to execute another command and print out statistics • Modify doit to become a basic shell that prompts for and executes commands • Modify your shell to become shell2 to execute commands in the background Introduction

3. Purpose • To practice using the fork and exec facilities of Unix/Linux • To learn how to find and use on-line documentation about system calls and system facilities. • man pages • To be accustomed to speaking directly with the operating system Introduction

4. Part 1: doit • doit command:– • Take another command line as argument • Execute that command • Print out statistics about command • Must compile and execute on your virtual machine • Likely to be compatible with most modern Linux systems • May not use system() system call • Helpful hints:– • fork(), execvp(), wait() • getrusage(), gettimeofday() Introduction

5. Part 1 (output) % doit cat /etc/motd /* print the current message of the day */ /* statistics about the cat command */ Introduction

6. Part 2: shell • Repeatedly prompt for command lines • Execute each command and print out statistics, as in doit • Implement special “built-in” commands • exit • cd dir • Special conditions • Input from stdin • Exit on end of file • Complain about illegal commands • Check for line length, number of arguments Introduction

7. Part 2 output % shell ==>cat /etc/motd /* print the current message of the day */ /* statistics about the cat command */ ==>cd dir /* current directory is changed to dir */ ==>ls /* listing of files in current directory */ /* statistics about this ls command */ ==>exit % /* back to your previous Linux prompt */ % shell < filename.txt /* reads, echoes, and executes each command/* /* statistics about each command */ /* exits after last command is completed */ Introduction

8. Part 3: Background execution (shell2) • Modify shell to allow executing commands in background, indicated by ‘&’ character • Causes shell to prompt for next command before previous command is complete • jobs built-in command lists background tasks in progress • Report completion at next opportunity • I.e., the next time user types a command, but before executing that command Introduction

9. Part 3 output % shell2 ==>numbercrunch & [1] 12345 /* indicate background task #1, process id */ ==>jobs [1] 12345 numbercrunch /* print process id and command name for tasks */ ==>ls /* listing of files in the current directory */ /* statistics about this ls command */ ==>cat /etc/motd [1] 12345 Completed < background job command > /* statistics about background job */ /* print the current message of the day */ /* statistics about this cat command */ ==>exit % /* back to your previous Linux prompt */ Introduction

10. Work environment • Please do this work on your virtual machine • You may use C or C++ • Note: • Your programs will probably be compatible with other Linux systems on campus • However, not all C/C++ compilers and Linux kernels are alike • Some may produce or ignore various warnings • Your virtual machine is the one that counts Introduction

11. Project submission • Due Thursday, January 24, 6:00 PM • Submit via web-based Turnin • Project name = Project 1 • Put your name at top of every file! (You would be surprised how many students forget!) Introduction

12. Project Submission (continued) • Code of your solution • Makefile • make clean • make all • make doit • make shell • make shell2 • One or more test cases • Write-up explaining everything • DO NOT • Put different parts of projects in folders • Zip files together • Create different Makefiles for different parts Introduction

13. Grading • Fifteen point project • Five points for each part • Point allocation per part • Correct compilation and build; no warnings! – 1 pt. • Correct execution of graders’ test cases – 2 pts. • Submission of own test cases – 1 pt • Write-up explaining what you did and your results • MS Word or PDF • No credit for a part if it fails to build Introduction

14. Not a team project! • Each student must submit own solution • Encouraged to discuss general approach, meaning of system calls, etc., with friends • Encouraged to seek help if puzzled by some concept, system call, etc. • Distill all discussions into your own work! Introduction