July 31st, 2013, 01:39 PM
I've read many tutorials both good and bad about C but only one contained a sigle page on signals and how they work etc.
I want to better understand them and the referance manual for the availible functions from glibc is not a good place to learn.
Does anyone else know some good free resources out there?
July 31st, 2013, 02:12 PM
What exactly are you looking for here? Are the man pages not detailed enough? On Ubuntu Linux, if you run:
man 2 signal
man 7 signal
You get fairly comprehensive docs on how the function works, a list of different signal types, a list of safe functions that can be used in a signal handler, what to return from your signal handler etc. from those two manual pages. Is there any particular piece of information you're looking for?
Up the Irons
What Would Jimi Do? Smash amps. Burn guitar. Take the groupies home.
"Death Before Dishonour, my Friends!!" - Bruce D ickinson, Iron Maiden Aug 20, 2005 @ OzzFest
Down with Sharon Osbourne
"I wouldn't hire a butcher to fix my car. I also wouldn't hire a marketing firm to build my website." - Nilpo
July 31st, 2013, 02:13 PM
The subject of signals and signal handling is usually covered in Linux/UNIX system programming. Or in shell scripting, which would at least offer a perspective on the subject, albeit not a C perspective.
Some years ago I downloaded a book, Advanced Linux Programming, for free. It might still be out there.
August 19th, 2013, 11:31 AM
Found it thanks!
Originally Posted by dwise1_aol
I'm talking about how to determine if you should block a signal or handle it or what. This might seem like a basic thing but some library functions like fopen return EINTR if a signal is received during it's execution. Their are other library functions that also return EINTR if a signal is received during execution I don't know all of them.
Here's my source for this info:
August 21st, 2013, 06:13 PM
I accidentally discovered that if you send sigusr1 to fluent it finishes the current iteration, saves the results and continuation files, then returns control to the user.
[/code] are essential for python code and Makefiles!