05-27-2008
I get what you guys mean.
I ran some test code using usleep and found some interesting results.
When i put usleep to 0.1secs, the actual sleeping time varies from the set point (0.1secs) with an error of about +5%. The same error percentage jumps to about +40% when i put usleep to 0.01sec and the same error jumps to about +300%(!!!!) when i put usleep to 0.001sec.
Looks like as the timer resolution is brought down the error keeps increasing. Could be due to system timer resolution as mentioned as well as the priority based scheduling employed by linux.
Anyway thanks a lot guys.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
HI,
I need to handle SIGUSR2 signal in my application to change the state of the application dynamically. I have implemented the signal handler. However the application is able to catch only one SIGUSR2 signal. The second SIGUSR2 signal causes the application to crash. This is happning only with... (3 Replies)
Discussion started by: diganta
3 Replies
2. UNIX for Advanced & Expert Users
Hi
can any please tell me
is it possible to catch the signal in a shell script like we do in C.
if yes please give me some idea or a link. (4 Replies)
Discussion started by: Raom
4 Replies
3. Programming
Hi folks
I'm trying to write a signal handler (in c on HPUX) that will catch the child process launched by execl when it's finished so that I can check a compliance file.
The signal handler appears to catch the child process terminating however when the signal handler completes the parent... (3 Replies)
Discussion started by: themezzaman
3 Replies
4. Shell Programming and Scripting
Guys,
I'm doing signal handling in Perl. I'm trying to catch ^C signal inside the script.
There two scripts : one shell script and one perl script.
The shell script calls the perl script.
For e.g. shell script a.sh and perl scipt sig.pl.
Shell script a.sh looks something like this :... (6 Replies)
Discussion started by: obelix
6 Replies
5. Programming
Hi,
I have a main loop which calls a sub loop, which finally returns to the main loop itself. The main loop runs when a flag is set. Now, I have a signal handler for SIGINT, which resets the flag and thus stops the main loop. Suppose I send SIGINT while the program is in subloop, I get an error... (1 Reply)
Discussion started by: Theju
1 Replies
6. Programming
Hi guys,
this is my first posting, so at first hi to everyone! ;)
I have a problem with ucontext_t in connection with signal handling. I want to simulate a preemptive scheduler. I am using the iTimer with ITIMER_PROF, to schedule the interrupts. You find the code below:
#include <stdio.h>... (18 Replies)
Discussion started by: XComp
18 Replies
7. Programming
I am trying to write a small program where I can send signals and then ask for an action to be triggered if that signal is received. For example, here is an example where I am trying to write a programme that will say you pressed ctrl*c when someone presses ctrl+c. My questions are what you would... (1 Reply)
Discussion started by: #moveon
1 Replies
8. Programming
i wrote handler for sigsegv such that i can allocate memory for a variable to which
sigsegv generated for illlegal acces of memory.
my code is
#include <signal.h>
#include<stdio.h>
#include<stdlib.h>
#include<string.h>
char *j;
void segv_handler(int dummy)
{
j=(char *)malloc(10);
... (4 Replies)
Discussion started by: pavan6754
4 Replies
9. UNIX and Linux Applications
Hello,
Can anybody tell me how can i handle segmentation fault signal, in C code? (2 Replies)
Discussion started by: mustus
2 Replies
10. Programming
hi friends i have a problem in signal handling ...
let me explain my problem clearly..
i have four process ..
main process forks two child process and each child process again forks another new process respectively...
the problem is whenever i kill the child process it is reforking and the... (2 Replies)
Discussion started by: senvenugopal
2 Replies
USLEEP(P) POSIX Programmer's Manual USLEEP(P)
NAME
usleep - suspend execution for an interval
SYNOPSIS
#include <unistd.h>
int usleep(useconds_t useconds);
DESCRIPTION
The usleep() function shall cause the calling thread to be suspended from execution until either the number of realtime microseconds speci-
fied by the argument useconds has elapsed or a signal is delivered to the calling thread and its action is to invoke a signal-catching
function or to terminate the process. The suspension time may be longer than requested due to the scheduling of other activity by the sys-
tem.
The useconds argument shall be less than one million. If the value of useconds is 0, then the call has no effect.
If a SIGALRM signal is generated for the calling process during execution of usleep() and if the SIGALRM signal is being ignored or blocked
from delivery, it is unspecified whether usleep() returns when the SIGALRM signal is scheduled. If the signal is being blocked, it is also
unspecified whether it remains pending after usleep() returns or it is discarded.
If a SIGALRM signal is generated for the calling process during execution of usleep(), except as a result of a prior call to alarm(), and
if the SIGALRM signal is not being ignored or blocked from delivery, it is unspecified whether that signal has any effect other than caus-
ing usleep() to return.
If a signal-catching function interrupts usleep() and examines or changes either the time a SIGALRM is scheduled to be generated, the
action associated with the SIGALRM signal, or whether the SIGALRM signal is blocked from delivery, the results are unspecified.
If a signal-catching function interrupts usleep() and calls siglongjmp() or longjmp() to restore an environment saved prior to the usleep()
call, the action associated with the SIGALRM signal and the time at which a SIGALRM signal is scheduled to be generated are unspecified. It
is also unspecified whether the SIGALRM signal is blocked, unless the process' signal mask is restored as part of the environment.
Implementations may place limitations on the granularity of timer values. For each interval timer, if the requested timer value requires a
finer granularity than the implementation supports, the actual timer value shall be rounded up to the next supported value.
Interactions between usleep() and any of the following are unspecified:
nanosleep()
setitimer()
timer_create()
timer_delete()
timer_getoverrun()
timer_gettime()
timer_settime()
ualarm()
sleep()
RETURN VALUE
Upon successful completion, usleep() shall return 0; otherwise, it shall return -1 and set errno to indicate the error.
ERRORS
The usleep() function may fail if:
EINVAL The time interval specified one million or more microseconds.
The following sections are informative.
EXAMPLES
None.
APPLICATION USAGE
Applications are recommended to use nanosleep() if the Timers option is supported, or setitimer(), timer_create(), timer_delete(),
timer_getoverrun(), timer_gettime(), or timer_settime() instead of this function.
RATIONALE
None.
FUTURE DIRECTIONS
None.
SEE ALSO
alarm() , getitimer() , nanosleep() , sigaction() , sleep() , timer_create() , timer_delete() , timer_getoverrun() , the Base Definitions
volume of IEEE Std 1003.1-2001, <unistd.h>
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE
and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained
online at http://www.opengroup.org/unix/online.html .
IEEE
/The Open Group 2003 USLEEP(P)