Re: alarm() not working as expected

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

> 1) When timeout occur (errno = EINTR), the program will continue to get
> the timeout error without at least waiting for timeout to occur again
> (which is set to 10 secs).  Below is a code snap shot.
That's strange. I've never seen this happen. Do you have other software 
running that might be sending you a SIGALRM signal?  Or another signal?
EINTR means that the API call was interrupted by a signal, but it isn't 
necessarily the signal that alarm() generated.
The signal number that's received is passed as a parm to your signal 
handler, you could try printing it out to see whether it's SIGALRM or 
whether it's something else.
I can think of things you could try to work around the problem, but I 
can't think of anything (aside from someone calling you with a signal) 
that would cause the problem you're experiencing.