It appears that MySql is doing funny things to SIGALRM.
No, it doesn't. It's the first bullet. The alarm signal is received. C calls are not interruptible, so calling the handler is delayed until the C code returns. alarm is working as expected.
1) Is this problem fixable?
You can interrupt C code by using unsafe signals, but it can leave the process in a weird state.
2) The whole purpose of this exercise is to find a way to get out of the MySql operation if it takes longer than 5 sec. to do MySql.
Perhaps you should start a thread with that question.
In reply to Re^7: Perl Alarm Not Working
by ikegami
in thread Perl Alarm Not Working
by aceofspace
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |