X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 20 Aug 2008 16:02:30 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cygrunsrv pause Message-ID: <20080820140230.GO29104@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <859402 DOT 88735 DOT qm AT web36202 DOT mail DOT mud DOT yahoo DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <859402.88735.qm@web36202.mail.mud.yahoo.com> User-Agent: Mutt/1.5.16 (2007-06-09) 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 On Aug 20 06:41, Unknown wrote: > Because I want to put the thread in suspend mode, instead of just stopping and restarting. I don't want the cron to start from the beginning. I'm not sure what the difference is, behaviour-wise, and I'm also not sure if cron doesn't choke on this (cron is known for problems resulting from jumps in the current timestamp), but you can simply try to send SIGSTOP/SIGCONT from an administrative account to the cron process, like this: kill -STOP $(cat /var/run/cron.pid) kill -CONT $(cat /var/run/cron.pid) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/