Subj : Re: sigwait() is not catching SIGUSR1 signal
To   : comp.programming.threads,comp.unix.programmer
From : Villy Kruse
Date : Mon Mar 14 2005 08:36 am

On Sat, 12 Mar 2005 10:37:14 -0500,
    Joe Seigh <jseigh_01@xemaps.com> wrote:


> On 12 Mar 2005 07:24:08 -0800, Neelakantan <neelakantan@cins.unipune.ernet.in> wrote:
>
>> Hi,
>>    If linuxThreads behaves so, Is it not violating the semantics that
>> is mentioned in the man page of sigwait()?. I despiratly need a way
>> out from this problem?
>> Any suggestions will be highly appreciated.
>>
> Try learning how to use pthread_cond_(signal|broadcast|wait|timedwait).
> You shouldn't use unix signals unless you literally want to do something
> in the worst way.  And if you want to do something in the worst way
> possible, don't expect anyone else to waste time trying to help you.
>


It was mentiond this was RedHat version 9, and this version introduced
the NPTL version of pthreads, which claims to be more conforming to
the standard than the old linux threads were.  For old linux kernels
the pthreads had to use SIGUSR for its internal purpose as no other signals
were available.  With current kernels this should not be required.


Villy

.