Processes, 7 of 8

[transcript]

[sample code discussed]

Note: As we saw in some earlier videos, the sample code here lacks a required call to perror(). If an exec fails, call perror() with the program you were trying to exec (the first argument to exec), so as to print an error message which will be much more useful to the user of your program than a generic error message which doesn't say what actually went wrong.

(And exit with exit status 1, not 0.)

All videos in this unit:

• Processes #1 (watch by July 5)
• Processes #2 (watch by July 5)
• Processes #3 (watch by July 5)
• Processes #4 (watch by July 5)
• Processes #5 (not required)
• Processes #6 (watch by July 5)
• Processes #7   ← you are here
• Processes #8 (optional)

All units (so far):

• The unix command line (watch by May 17)
• Software tools (watch by May 17)
• Shell programming (watch most in the week of May 17; one more by July 26)
• The make command
• Introductory C (watch by May 31)
• Introduction to arrays in C (watch by May 31)
• Pointers in C (watch by June 7)
• Files in C (watch by June 14)
• Strings in C (watch by June 14)
• struct (watch by June 7)
• The C declaration syntax (watch by July 5)
• The C pre-processor (watch by July 19)
• Dynamic memory allocation (malloc()) (watch by July 5)
• The unix filesystem (watch by July 5)
• Processes   ← you are here
• Signals (watch by July 12)
• Bitwise operations in C (watch by July 12)
• sockets (optionally watch in August)
• select() (watch by July 19)
• Concurrency (watch by August 2)

Overall course schedule:

• Course schedule