X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Date: Fri, 16 Dec 2011 14:42:45 -0600 From: Mike Brown To: cygwin AT cygwin DOT com Subject: Re: cron still not working - even after rerunning cron config Message-ID: <20111216204245.GG14806@mrvideo.vidiot.com> References: <20111216203108 DOT GE14806 AT mrvideo DOT vidiot DOT com> <4EEBAC43 DOT 8060603 AT bopp DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EEBAC43.8060603@bopp.net> User-Agent: Mutt/1.5.17 (2007-11-01) 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 Fri, Dec 16, 2011 at 02:38:27PM -0600, Jeremy Bopp wrote: > Sorry that I can't help you with your cron problem, but have you > considered using the Windows Task Scheduler instead given the urgency of > your situation? It can be used to kick off Cygwin processes just like > any other. You'll need to wrap your existing tasks with a script in > order to ensure that they receive the right environment, but that may be > easier than debugging cron at this time. I hate the Windblows task scheduler. Plus, while I am away I might have to remotely get in via ssh (which also doesn't work) and change/add entries. That is best done using text editing. MB -- e-mail: vidiot AT vidiot DOT com | vidiot AT vidiot DOT net /~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there. Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple