From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10893 invoked by alias); 11 May 2004 22:40:08 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 10886 invoked from network); 11 May 2004 22:40:07 -0000 Received: from unknown (HELO ns2.prospeed.net) (12.46.111.132) by sourceware.org with SMTP; 11 May 2004 22:40:07 -0000 Received: from enterprise-e.cygwin.com ([12.46.110.44]) by ns2.prospeed.net (8.12.10/8.12.8) with ESMTP id i4BMntfc012811; Tue, 11 May 2004 18:49:55 -0400 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040511183007.031c4240@127.0.0.1> X-Sender: Date: Tue, 11 May 2004 23:11:00 -0000 To: "Jimmy Hayes" , From: Larry Hall Subject: Re: cron In-Reply-To: <75EA21FE420C864D895DE6E87383D6A157EA41@exchange1.meddatahc s.com> References: <75EA21FE420C864D895DE6E87383D6A157EA41@exchange1.meddatahcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2004-05/txt/msg00423.txt.bz2 At 06:07 PM 5/11/2004, you wrote: >Hi I scheduled a script to run at a 7:00 am trough cron but it never >runs. Any ideas? Sure. Start here: >Problem reports: http://cygwin.com/problems.html Follow that by: >I even leave the cygwin window open. That's not necessary if you've installed cron properly and you're running it as a service. The above should help you find some problems and key you in on the procedure and information required when reporting problems to this list. HTH, -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/