2.4 linux SIGALRM

[krish_kish]

Hi,

We are using setitimer on 2.4 linux in our application to set the
time and registering
signal handler with SIGALRM. So, signalhandler will be called for
every 'x' milliseconds.

We are now planning to use this application on 2.6 linux.

We found the following behaviour.
(1) The signal handler is taking more than the ALRM time (more
than 'x' milliseconds)
(2) Another timer expiry is happening and another signal
handler is called.

We have observed that before the first signal handler function
returned, another signal handler
call is happening.

We have following questions.
Q1) Is this behaviour possible?
Q2) We understand that if this behaviour occurs, signals
should get queued.
On 2.4 linux, these will get queued.
How do we achieve this behaviour on 2.6 linux?
Q3) Are setitimer() functions deprecated in 2.6 linux?

Regards,
Kishore.