From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3469 invoked by alias); 10 Jan 2003 19:23:09 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 3450 invoked from network); 10 Jan 2003 19:23:08 -0000 Received: from unknown (HELO sotr0085.cognos.com) (205.210.232.62) by 209.249.29.67 with SMTP; 10 Jan 2003 19:23:08 -0000 Received: by sotr0085.cognos.com with Internet Mail Service (5.5.2653.19) id ; Fri, 10 Jan 2003 14:22:25 -0500 Message-ID: From: "Bossom, John" To: 'Roy Riggs' , pthreads-win32@sources.redhat.com Subject: RE: Way to wake up sleeping threads? Date: Fri, 10 Jan 2003 19:23:00 -0000 MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2003/txt/msg00004.txt.bz2 What do you mean by "sleeping"? If you are blocked on a socket, then use a timeout for the socket and check a flag to see if you should quit, else, block on the socket again. Otherwise, use a synchronization object, such as a semaphore to "sleep" and post to it to wake it up. pthread_kill involves signal handling which does not map well to win32. -----Original Message----- From: Roy Riggs [mailto:rriggs@edgenet.com] Sent: Friday, January 10, 2003 2:12 PM To: pthreads-win32@sources.redhat.com Subject: Way to wake up sleeping threads? I'm trying to port some code that was using pthread_kill() to wake up a sleeping thread. Is there some other means of doing this with this implementation of pthreads, since it doesn't support pthread_kill() ? Thanks, Roy ------------------------------------- Roy Riggs Director, Software Development Edgenet Inc. w: 615.234.3836 e: rriggs@edgenet.com NOTICE: This email and any attached files are confidential and intended solely for the use of the addressee. If you have received this email in error, please notify the sender and delete it immediately, without disclosing or using its contents for any purpose. Edgenet Inc accepts no liability for any damage caused by any virus transmitted by this email. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.