Using C on the UNIX System

I have taken several “c” courses. And dabbled in many platforms. Yet the courses seem to have completely overlooked signals other than a few traps. I now work in global services to help people if a function is not functioning. However, most of the questions posed were signal-related. Where did they come from? What do I do with them? The book is a bit dated, but the descriptions are still relevant, and how to handle signals is still relevant. Of course, the environment is a tad more convoluted with more complex environments. In AIX, we can look at /usr/include/sys/signal.h to see which numbers apply to which signals and get a general idea of how to treat them. Topics include: I/O without using stdio Manipulating files and directories Device I/O control Getting information about users Telling time and timing things Processing signals Creating, processing, and executing programs Job control Interprocess communications Networking (Internet client and server) Pseudo terminals Reading kernel data structures

I bought this book by my own in order to understand and go a little bit deep about system calls. And this book was what I was expecting. If you are a beginer C programmer and want to get into UNIX programming this book is for you. Even though the book is like 20 years old is was just perfect for me because I was just beginning with system calls and UNIX programming. And besides, C language is almost not changed within 20 years. So, source code samples run almost without modifications. Maybe some definitions and types might look weird but I you know the basics of C this should not be a problem for you.