Difference between revisions of "Operating Systems 2019W Lecture 6"
Jump to navigation
Jump to search
(→Video) |
(→Notes) |
||
| Line 9: | Line 9: | ||
* signal handlers | * signal handlers | ||
* I/O redirection | * I/O redirection | ||
===In Class=== | |||
<pre> | |||
Lecture 6 | |||
--------- | |||
Topics | |||
- signal handlers | |||
- I/O redirection | |||
- environment variables & command line arguments | |||
Key ideas for signals | |||
* processes can register signal handler functions for specific signals | |||
* When the kernel delivers a signal to a process, it runs the specified handler | |||
* The C library defines default handlers for all signals (except STOP and KILL) | |||
* When a process gets a signal, current execution is interrupted and the handler | |||
is invoked. When the handler terminates, the process continues where it was | |||
* If the process was blocked on a system call, the system call is interrupted | |||
and the handler is run. | |||
* The standard library can do different things with interrupted system calls | |||
</pre> | |||
Revision as of 22:24, 23 January 2019
Video
Video from the lecture given on January 23, 2019 is now available.
Notes
Topics for today
- environment variables
- signal handlers
- I/O redirection
In Class
Lecture 6 --------- Topics - signal handlers - I/O redirection - environment variables & command line arguments Key ideas for signals * processes can register signal handler functions for specific signals * When the kernel delivers a signal to a process, it runs the specified handler * The C library defines default handlers for all signals (except STOP and KILL) * When a process gets a signal, current execution is interrupted and the handler is invoked. When the handler terminates, the process continues where it was * If the process was blocked on a system call, the system call is interrupted and the handler is run. * The standard library can do different things with interrupted system calls