IT 251 Milestone Four Guidelines and Rubric Overview: Scripting is a very important skill to have when working as a *NIX system administrator and one…
IT 251 Milestone Four Guidelines and Rubric
Overview: Scripting is a very important skill to have when working as a *NIX system administrator and one that will make your day much less tedious and much more efficient. This milestone will have you work with basic scripting much in the same way you would within the information technology profession.
Prompt: For this milestone, you will complete several tasks assigned by your manager within the *NIX environment.
Specifically, the following critical elements must be addressed in this milestone:
- Scripting
One of your coworkers needs help with a script that he has been working on but cannot seem to get working. He has copied his bad script, superscript.sh, into your home directory under the scripts directory (~/scripts/superscript.sh). After correcting the script, build a simple script of your own to assist in retrieving user info from SLASH/etc/passwd and SLASH/etc/group to make user administration simpler.
- Correct the Script: Correct your coworker’s script, make the script executable (owner and group, not world), execute the corrected script, take a screenshot of the entire script code, take a screenshot of the executed script output, and describe each correction you made to the script to get it working and explain why you made those changes.
- Script
code (screenshot):
- Executed
script output (screenshot):
- Description of each correction made to the script and why:
- User Administration Script: Create a script that will assist in retrieving user information and meet the following requirements:
- Script will be built in your ~/scripts directory and should be named userlookup.sh.
- On the second line from the top of the script, below the #!, add a commented line with your name, course, and date followed by a blank newline.
- Build your script
so it takes the supplied first name of a user and returns the indicated output.
The script should retrieve information for the user the script is run against
and an error message if no user is found. Users to test will be Bob, Henry, and
Notaperson. Bob and Henry should return the correct information and Notapersonshould
return an error message of no such person found (as there is no Notaperson
user).
- To run script input format:
sh userlookup.sh bob
sh userlookup.sh henry
sh userlookup.sh notaperson
- Expected output format (will differ based on the user and will display an error when a user is not found):
bob:x:1001:1001:Ops:/home/bob:/bin/bash
bob:x:1001:
ops:x:1004:bob, franks
- You may want to test various commands in the
shell itself to get the output you are looking for and then move the pieces
that prove to work as expected into the script to get the desired final output.
- Set the permissions on userlookup.sh to owner and group executable (not world) and execute the script three times—once for Bob, Henry, and Notaperson—in the format shown above.
- Screenshot the code for your entire script.
- Screenshot the outputs from executing the script all three times.
- Write a couple of sentences detailing your thought process and reasoning for utilizing the commands you used within your script.
- Screenshot
the code for your entire script and paste the screenshot(s) here:
- Screenshot
the outputs from executing the script all three times and paste the
screenshot(s) here:
- Write a couple of sentences detailing your thought process and reasoning for utilizing the commands you used within your script:
Work
Verification: Take a
screenshot (or multiple screenshots if needed) that captures the output of the pwd and history commands. Paste these screenshots here:
Rubric
Guidelines for Submission: Be sure to read the primary Final Project Guidelines and Rubric document in full, as it contains the context that each milestone is based within and provides the complete picture of the final project that each milestone builds on. Your answers will be inserted directly into this document and saved. Tasks marked in red indicate that an answer and/or screenshot is expected.
Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information, review these instructions.
| Critical Elements | Proficient (100%) | Needs Improvement (55%) | Not Evident (0%) | Value |
| Scripting: Correct the Script | Accurately corrects the script, makes it executable, and executes the script as illustrated by the necessary screenshots | Attempts to correct the script and make it executable, but the task has errors or unprofessional elements in the scripting that make it not executable or is not clearly illustrated by the necessary screenshots | Does not correct the script, make it executable, or execute the script | 35 |
| Scripting: User Administration Script | Accurately creates a script that meets the requirements as illustrated by the necessary screenshots | Creates a script that meets the requirements, but the task has errors or unprofessional elements in the scripting or is not clearly illustrated by the necessary screenshots | Does not create a script that meets the requirements | 35 |
| Console History and Work Verification | Accurately captures most output and the work thus far as illustrated by the necessary screenshot(s) | Captures some of the output and the work thus far as illustrated by the necessary screenshot(s) | Does not capture the output or the work thus far | 15 |
| Articulation of Response | Submission has no major errors related to citations, grammar, spelling, syntax, or organization | Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas | Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas | 15 |
| Total | 100% |