Systems Admininstration Scripting Log

Topics: Signal, Process, File system Pages: 2 (268 words) Published: August 22, 2011
University of Phoenix Material

Systems Administration Scripting Log

Date: 08/01/2011

As you complete each step listed below, keep track of what occurs at each point: what you type and the output given, as well as if you experience any errors. Submit this information in a log to your instructor for this week’s assignment. Your log can use the sample format provided, or create your own.

1. In the same folder as last week, create a new file called week4prog1[name].scr. 2. Change the permissions on this new file to add the execute bit for user, group, and owner. chmod 777 week4hector.scr

3. Run the script below:

a. #!/bin/bash

b. count=1
c. echo "start of the program"
d. while [ $count -le 10 ]
e. do
i. echo "Loop #$count"
ii. sleep 10
iii. count=$[ count + 1 ]
f. done
g. echo "end of the program

4. Modify the program to add a trap for SIGINT and SIGTERM.


5. Save the script and this time run the script in the background.

Bash week4Hector.scr &

6. Use the jobs command to display a list of the jobs currently running.


7. Find the process id of the script and kill the job.

kill bash 13268

8. Check to see if you get the trap message.

No trap message

9. Run the script again using the at command to schedule the job in the future. Wait for the job to run to make sure it executes.

at -f week4Hector.scr –m 17:45
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Log in System Essay
  • Log in Log Out Payroll System Essay
  • Scripting Essay
  • logs Essay
  • SYSTEMS Essay
  • Scripting Essay
  • Infromation systems Essay
  • Management System Essay

Become a StudyMode Member

Sign Up - It's Free