Its always best to keep it simple.
Most texts you read on signals recommend getting out of the handler ASAP.
A simple way it just use the handler to set a flag.
Hi Everybody,
I have gone through man of sigwait and new to UNIX signals. Could anyone explain me about the following lines mentioned in sigwait man help ?
"The selection of a signal in set is independent of the signal
mask of the calling thread or LWP. This means a thread or
LWP can ... (1 Reply)
Hello,
Can anyone, please, guide me on the use of nanosleep. I'm learning threads. I want to introduce a delay (not nested for loops, something more customizable). Nanosleep looked useful (or any other form of customizable and easy-to-use delay). Sleep is too long. :) (2 Replies)
Hi,
Ho do I differentiate system call from library call?
for example if I am using chmod , how do I find out if it is a system call or library call?
Thanks
Muru (2 Replies)
Hi,
I have encountered the following problem on Solaris 10:
I have a thread that is asleep on nanosleep (set to 24 hours).
Something that happens on another thread, causes the nanosleep to exit, even though the time has not elapsed.
The returned value is 0 (so it doesn't look like it... (1 Reply)
Hi,
I have a daq program that runs in an infinite loop until it receives SIGINT. A handler catches the signal and sets a flag to stop the while loop. After the loop some things have to be cleaned up.
The problem is that I want my main while loop to wait until the next full second begins, to... (2 Replies)
Hello,
I have a problem with package and name space.
require "/Mehran/DSGateEngineLib/general.pl";
use strict;
sub System_Status_Main_Service_Status_Intrusion_Prevention
{
my %idpstatus;
my @result;
&General_ReadHash("/var/dsg/idp/settings",\%idpstatus);
#print... (4 Replies)
Application runs on both solaris 6 and 10.
solaris 6 having only posix4.so library, solaris 10 having libposix4.so and librt.so
Can we link application to lposix4 instead of lrt for nanosleep, sothat application will run in both machines? (2 Replies)
Discussion started by: satish@123
2 Replies
LEARN ABOUT MOJAVE
usleep
USLEEP(3) BSD Library Functions Manual USLEEP(3)NAME
usleep -- suspend thread execution for an interval measured in microseconds
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
usleep(useconds_t microseconds);
DESCRIPTION
The usleep() function suspends execution of the calling thread until either microseconds microseconds have elapsed or a signal is delivered
to the thread and its action is to invoke a signal-catching function or to terminate the process. System activity or limitations may
lengthen the sleep by an indeterminate amount.
This function is implemented using nanosleep(2) by pausing for microseconds microseconds or until a signal occurs. Consequently, in this
implementation, sleeping has no effect on the state of process timers, and there is no special handling for SIGALRM. Also, this implementa-
tion does not put a limit on the value of microseconds (other than that limited by the size of the useconds_t type); some other platforms
require it to be less than one million.
NOTE
The usleep() function is obsolescent. Use nanosleep(2) instead.
RETURN VALUES
The usleep() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate
the error.
ERRORS
The usleep() function will fail if:
[EINTR] A signal was delivered to the process and its action was to invoke a signal-catching function.
SEE ALSO nanosleep(2), sleep(3)HISTORY
The usleep() function appeared in 4.3BSD.
BSD February 13, 1998 BSD