Message-ID: <4EEBB7B4.5020103@arlut.utexas.edu>
Date: Fri, 16 Dec 2011 15:27:16 -0600
From: Jesse Ziser <ziser@arlut.utexas.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: cron still not working - even after rerunning cron config
References: <20111216203108.GE14806@mrvideo.vidiot.com> <4EEBAC43.8060603@bopp.net> <20111216204245.GG14806@mrvideo.vidiot.com>
In-Reply-To: <20111216204245.GG14806@mrvideo.vidiot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 12/16/2011 2:42 PM, Mike Brown wrote:
> 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.

You could always use remote desktop if you're having problems with ssh 
(again, given the urgency of your situation).

--
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