Sponsored Content
Top Forums Programming How to cancel a thread safely from the initial thread? Post 70471 by alan.zhao on Friday 29th of April 2005 03:44:01 AM
Old 04-29-2005
How to cancel a thread safely from the initial thread?

how about asynchronous canceling?
or with signal?
if with signal whether it effects the process?
my english so badly Smilie Smilie
 

3 More Discussions You Might Find Interesting

1. Programming

Parent Thread Of Child Thread

Parent Thread Of Child Thread Suppose a process creates some threads say threadC and threadD. Later on each of these threads create new child threads say threadC1, threadC2, threadC3 etc. So a tree of threads will get created. Is there any way to find out the parent thread of one such... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

2. UNIX for Dummies Questions & Answers

Difference between handle to the thread HANDLE and thread identifier pthread_t

This question might be silly but its confusing me a bit: What is the difference between handle to the thread HANDLE and thread identifier pthread_t? ---------- Post updated at 01:52 PM ---------- Previous update was at 01:48 PM ---------- Sorry I saw details and HANDLE is in windows and... (0 Replies)
Discussion started by: rupeshkp728
0 Replies

3. Forum Support Area for Unregistered Users & Account Problems

Not able to post thread/reply to thread

Dear Moderator I am not able to post any new thread or post reply to mine old thread. Kindly help as i am stuck on one problem and needed suggestion. Regards Jaydeep (1 Reply)
Discussion started by: jaydeep_sadaria
1 Replies
usleep(2)							System Calls Manual							 usleep(2)

NAME
usleep - suspend execution for an interval SYNOPSIS
DESCRIPTION
The function will cause the calling thread to be suspended from execution until either the number of real-time microseconds specified 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 activities by the system, or because of the time spent in processing the call. The useconds argument must be less than 1,000,000. If the value of useconds is 0, then the call has no effect. If a signal is generated for the calling process during execution of and if the signal is being ignored or blocked from delivery, it is unspecified whether returns when the signal is scheduled; if the signal is being blocked, it is also unspecified whether it remains pending after returns or it is discarded. If a signal is generated for the calling process during execution of except as a result of a prior call to and if the signal is not being ignored or blocked from delivery, it is unspecified whether that signal has any effect other than causing to return. If a signal-catching function interrupts and examines or changes either the time a is scheduled to be generated, the action associated with the signal, or whether the signal is blocked from delivery, the results are unspecified. If a signal-catching function interrupts and calls or to restore an environment saved prior to the call, the action associated with the signal and the time at which a signal is scheduled to be generated are unspecified, it is also unspecified whether the signal is blocked, unless the process's 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 will be rounded up to the next supported value. Interactions between and any of the following are unspecified: RETURN VALUE
On successful completion, returns 0. Otherwise, it returns -1 and sets to indicate the error. ERRORS
The function may fail if: [EINVAL] The time interval specified 1,000,000 or more microseconds. APPLICATION USAGE
The function is included for its historical usage. The function is preferred over this function. Multi-threaded applications are recom- mended to use instead of is also a thread canceling point. SEE ALSO
alarm(2), getitimer(2), nanosleep(2), sigaction(2), sleep(3C), timer_create(2), timer_delete(2), timer_getoverrun(2), timer_gettime(2), timer_settime(2), <unistd.h>. CHANGE HISTORY
First released in Issue 4, Version 2. usleep(2)
All times are GMT -4. The time now is 07:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy