08-26-2001
threads programming
Hi,
If you are new to C and UNIX, threads programming
is probably going to be a bit complex. It is
in fact an advanced programming topic. You may
want to read up a bit more on this topic first.
I would recommend "Pthreads Programming" published
by O'Reilly or "Programming with POSIX Threads"
published by Addison-Wesley. Based on the errors
your getting, it looks like a problem with your
code if the first error you actually get is the
"syntax error" (even though it says it was
encountered in pthreads.h). It may help to
attach the source for "mythread.c".
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi, someone knows about a Load Generator for web?, I´ve been searching the web and I found "Astra Test", but I doesn´t work.
Thanks! :) (3 Replies)
Discussion started by: momo
3 Replies
2. UNIX for Dummies Questions & Answers
All,
Have an AMD-K6/2 PC, 20G.Hd along with RH7.2.
Wanting to know what I should do in terms of setup (workstation/server) and then what I can do with it?
I'd like to learn a DBMS and SQL - can I do this using RedHat?
Any suggestions with how I can use/ what I can do with this appreciated. (3 Replies)
Discussion started by: Cameron
3 Replies
3. UNIX for Advanced & Expert Users
Hello there!
Slightly off topic maybe, but maybe someone can help us. For a videoshow which will be called reality 6.1 we need a video file from a unix kernel that is compiling. Does anyone know how to capture this, or does anyone have such a vid?
cheers,
iuno
(www.iuno.nl) (2 Replies)
Discussion started by: iuno
2 Replies
4. Shell Programming and Scripting
hi ,
i am writing a script to copy the MQ messages from onw queue to another. The following i got from one site, but i di not understand , can anyone explain.
/root/scripts/sap/q -m$Q_MANAGER -i$Q_NAME_SRC_1 -F/logs/mq/MQ_COPYdump_$Q_NAME_SRC_1.$$
/root/scripts/sap/q -m$Q_MANAGER... (0 Replies)
Discussion started by: Satyak
0 Replies
5. SCO
Hi guys!!! i have a sco unix 3.2 v4.2 floppy's but i don't have N1 boot disk!!
how to find it??? :confused:
thanks!! (sorry for my bad english!) (4 Replies)
Discussion started by: panos_pit
4 Replies
6. Programming
Hi to all,
i am trying to make a kernel call that will display the number of times each kernel call was called. Any idea where to look? I can't find the right files and also how to get all those values. Already made a kernel call that displays how many kernel calls are in the system. I am using... (6 Replies)
Discussion started by: hariscy
6 Replies
7. What is on Your Mind?
Greetings all!!
Have only recently signed up to this forum and I must say I am thoroughly impressed! :D
Everyone has been nothing but amazingly helpful and I haven't been made to feel like the newbie that I am.
I will definately be becoming a daily user of this site not only for help... (1 Reply)
Discussion started by: U_C_Dispatj
1 Replies
LEARN ABOUT REDHAT
pthread_kill_other_threads_np
PTHREAD_KILL_OTHER_THREADS_NP(3) Library Functions Manual PTHREAD_KILL_OTHER_THREADS_NP(3)
NAME
pthread_kill_other_threads_np - terminate all threads in program except calling thread
SYNOPSIS
#include <pthread.h>
void pthread_kill_other_threads_np(void);
DESCRIPTION
pthread_kill_other_threads_np is a non-portable LinuxThreads extension. It causes all threads in the program to terminate immediately,
except the calling thread which proceeds normally. It is intended to be called just before a thread calls one of the exec functions, e.g.
execve(2).
Termination of the other threads is not performed through pthread_cancel(3) and completely bypasses the cancellation mechanism. Hence, the
current settings for cancellation state and cancellation type are ignored, and the cleanup handlers are not executed in the terminated
threads.
AUTHOR
Xavier Leroy <Xavier.Leroy@inria.fr>
SEE ALSO
execve(2), pthread_setcancelstate(3), pthread_setcanceltype(3), pthread_cancel(3).
BUGS
According to POSIX 1003.1c, a successful exec* in one of the threads should terminate automatically all other threads in the program. This
behavior is not yet implemented in LinuxThreads. Calling pthread_kill_other_threads_np before exec* achieves much of the same behavior,
except that if exec* ultimately fails, then all other threads are already killed.
LinuxThreads PTHREAD_KILL_OTHER_THREADS_NP(3)