signalAlarmsOct10

signalAlarmsOct10 - TaskControl: SignalsandAlarms...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
Page 1 Task Control: Signals and Alarms Chapter 7 and 8 B. Ramamurthy
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Page 2 Multi-tasking How to create multiple tasks? Ex: Xinu create()  How to control them? ready() resched() How to synchronize them? How to communicate  among them?  XINU: semaphores, send and receive messages How to (software) interrupt a process? signals
Background image of page 2
Page 3 Examples Consider g++ myProg.c You want to kill this process after you started the  compilation. .hit cntrl-C Consider execution of a program called “badprog” >badprog It core dumps . . What happened? The error in the program  results in a signal to kernel to stop and dump the offending  code Consider “kill –p <pid>” Kill issues a termination signal to the process identified by  the pid
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Linux Processes Similar to XINU Procs. Lets understand how to create a linux  process and control it. Chapter 7 and 8 of text book. Chapter 7 : multi-tasking Chapter 8: Task communication and  synchronization Page 4
Background image of page 4
Page 5 Process creation Four common events that lead to a process  creation are: 1) When a new batch-job is presented for  execution. 2) When an interactive user logs in / system  initialization. 3) When OS needs to perform an operation (usually  IO) on behalf of a user process, concurrently with  that process. 4) To exploit parallelism an user process can  spawn a number of processes.      
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Page 6 Termination of a process Normal completion, time limit exceeded, memory  unavailable Bounds violation, protection error, arithmetic error, invalid  instruction IO failure, Operator intervention, parent termination,  parent request, killed by another process A number of other conditions are possible. 
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 10/27/2011 for the course CSE 321 at SUNY Buffalo.

Page1 / 20

signalAlarmsOct10 - TaskControl: SignalsandAlarms...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online