COMP 3000 Lab 6 2012: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This lab is due on Friday, Nov. 9, at 11:55 PM. | This lab is due on Friday, Nov. 9, at 11:55 PM. This lab has 16 points. | ||
Run the following three commands in bash. (Note the \ is just to note the command continues on the following line.) | Run the following three commands in bash. (Note the \ is just to note the command continues on the following line.) | ||
| Line 10: | Line 10: | ||
The following questions are based on these three lines. | The following questions are based on these three lines. | ||
# Describe the output of the above lines. In particular, how is the output of the two commands intermingled in the file race.txt? | # [2] Describe the output of the above lines. In particular, how is the output of the two commands intermingled in the file race.txt? | ||
# How could you modify the lines so that output to the file race.txt continues until | # [2] How could you modify the lines so that output to the file race.txt continues until the files "P1-done" or "P2-done" are created in the current directory (instead of testing the values of x and y)? | ||
# Approximately how many processes do these two lines generate on your system? How can you tell? | # [2] Approximately how many processes do these two lines generate on your system? How can you tell? | ||
# Change each line into a stand-alone shell script with no semicolons. | # [2] Change each line into a stand-alone shell script with no semicolons. | ||
# Use flock in the shell script versions of the commands to keep the output of the three echo's in the inner loop from being broken apart (make them "atomic"). Thus, in race.txt, you'll have lines starting with: | # [4] Change the shell scripts so that they never run concurrently using the flock command. If one is running, then the other should wait until it is finished. | ||
# [4] Use flock in the shell script versions of the commands to keep the output of the three echo's in the inner loop from being broken apart (make them "atomic"). Thus, in race.txt, you'll have lines starting with: | |||
P1 C1 ... | P1 C1 ... | ||
P1 C2 ... | P1 C2 ... | ||
Revision as of 16:10, 5 November 2012
This lab is due on Friday, Nov. 9, at 11:55 PM. This lab has 16 points.
Run the following three commands in bash. (Note the \ is just to note the command continues on the following line.)
x=0; while builtin test $x -lt 50000; do echo "P1 C1 $x"; echo "P1 C2 $x"; \ echo "P1 C3 $x"; let x=$(($x + 1)); done >> race.txt & y=0; while builtin test $y -lt 50000; do echo "P2 C1 $y"; echo "P2 C2 $y"; \ echo "P2 C3 $y"; let y=$(($y + 1)); done >> race.txt &
The following questions are based on these three lines.
- [2] Describe the output of the above lines. In particular, how is the output of the two commands intermingled in the file race.txt?
- [2] How could you modify the lines so that output to the file race.txt continues until the files "P1-done" or "P2-done" are created in the current directory (instead of testing the values of x and y)?
- [2] Approximately how many processes do these two lines generate on your system? How can you tell?
- [2] Change each line into a stand-alone shell script with no semicolons.
- [4] Change the shell scripts so that they never run concurrently using the flock command. If one is running, then the other should wait until it is finished.
- [4] Use flock in the shell script versions of the commands to keep the output of the three echo's in the inner loop from being broken apart (make them "atomic"). Thus, in race.txt, you'll have lines starting with:
P1 C1 ... P1 C2 ... P1 C3 ... P2 C1 ... P2 C2 ... P2 C3 ... P2 C1 ... P2 C2 ... P2 C3 ... P1 C1 ... P1 C2 ... P1 C3 ...
Note that the interleaving of output from P1 and P2 can be in any order so long as the sequence for each is always C1, C2, then C3. NOTE: You may want to avoid doing this on a non-local filesystem, e.g., don't put race.txt in your home directory on the Lambda machines. Doing this in a VM should work fine.