COSC 350 System Software Lab #6

COSC350 System Software
1
COSC 350 System Software Lab #6

How to submit
• For each program, you need write detailed comments for each statement.
• You need demonstrate each task in front of me during the next lab hours.
• Reference for Task2, Task3, and Task4, check the link on my homepage.
Task 1 : getenv() function
• Write your own getenv() function called mygetenv() function which has same syntax and
semantics.
• Write a simple C program to show your mygetenv() function works well.
Task 2: Creating New Processes using fork
A. Copy fork1.c from BLP 4
th edition, page 474.
B. Compile and run it to be sure you understand what it does.
C. Modify your fork1.c to take four command-line arguments:
1. Nc - number of iterations for child process
2. Np - number of iterations for parent process
3. Tc - sleep time for child process
4. Tp - sleep time for parent process
Then, modify the code accordingly.
D. Run the program as fork1 5 3 1 1. You should get the same result as running the original
version.
E. Run the program with the following values (and any other values you find interesting):
Nc Np Tc Tp
5 3 1 5
5 3 5 1
Task 3: Using wait
A. Copy your modified fork1.c to a file named forkWait.c.
COSC350 System Software, Spring 2021
2
B. Modify forkWait.c so the parent process waits for the child to finish. Use the code from
BLP 4th edition in page 475 (page 458 in 3rd edition), for the wait portion.
C. Print your modified forkWait.c to hand in.
D. Run your forkWait with Nc = 5, Np = 3, Tc = 1, and Tp = 1.
E. Briefly describe how your result differs from the original program in Task 2. Explain.
Task 4: fork with exec
This task forks a child process and uses exec to replace its process image with another image.
It's very similar to Task 3, but the child process is implemented as a separate program.
A. Copy forkWait.c from Task 4 to a file named forkExec.c
B. Modify forkExec.c so the child process image is replaced by the image of a program
named child. Use one of the exec family of functions to do this.
C. Write child.c to do the same thing as the child process did in Task 4.
o The child should give its pid each time it prints the message.
o The parent should give its pid each time it prints the message.
o The child program should take three command-line arguments, the message, Nc,
and Tc.
o To get an interesting exit status from the child, have it return 37, rather than 0.
Task 5 : file sharing between parent and child.
• Write a C program such that receive an input file name as an argument and open the file
as inputs. And then create a child process. Input file must open only one time and the
file descriptor is shared by parent and child process. Both the parent and the child read
a byte at a time from the input file and write output to independent files (parent.txt for
parent output, child.txt for child output). The parent process collect numeric characters
and child collect non-numberic characters. Without any form of synchronization, parent
and child process will create wrong output files.
• Modify the previous program and try to synchronize and get correct outputs for each
process.
Note)
o Do not open the input file twice for synchronization.
o Define your own function to check numeric character.
o Do not use vfork(), sleep(), wait() or waitpid() for synchronization.
o Check all possible errors for system calls