X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <859402 DOT 88735 DOT qm AT web36202 DOT mail DOT mud DOT yahoo DOT com> Subject: RE: cygrunsrv pause Date: Wed, 20 Aug 2008 15:04:24 +0100 Message-ID: <03fc01c902cd$a6d97470$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <859402.88735.qm@web36202.mail.mud.yahoo.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Unknown wrote on 20 August 2008 14:41: > Because I want to put the thread in suspend mode, instead of just > stopping and restarting. That's a problematical idea. What if the thread has just taken a critical system mutex when you suspend it? > I don't want the cron to start from the beginning. Why not? This is the heart of your question: the stuff about suspending the thread is just a means to acheive this goal, no? cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/