From: Larry Hall <cygwin-lh@cygwin.com>
To: "Jimmy Hayes" <jhayes@verilet.com>, <cygwin@cygwin.com>
Subject: Re: cron
Date: Tue, 11 May 2004 23:11:00 -0000 [thread overview]
Message-ID: <6.1.0.6.0.20040511183007.031c4240@127.0.0.1> (raw)
In-Reply-To: <75EA21FE420C864D895DE6E87383D6A157EA41@exchange1.meddatahc s.com>
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:
<http://www.cygwin.com/ml/cygwin/2004-03/msg00379.html>
>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/
next prev parent reply other threads:[~2004-05-11 22:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 22:11 cron Jimmy Hayes
[not found] ` <75EA21FE420C864D895DE6E87383D6A157EA41@exchange1.meddatahc s.com>
2004-05-11 23:11 ` Larry Hall [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-10 21:27 cron Rolf Schlagenhaft
2012-01-10 21:46 ` cron Larry Hall (Cygwin)
2012-01-10 23:45 ` cron Rolf Schlagenhaft
2011-08-24 16:09 cron mramakishore
2011-08-24 16:58 ` cron Larry Hall (Cygwin)
2011-08-28 10:50 ` cron kishore
2011-08-31 18:07 ` cron Larry Hall (Cygwin)
2009-09-16 7:51 cron Μηχανογράφηση ΔΔΕ Α΄ Αθήνας
2009-09-16 16:15 ` cron Pierre A. Humblet
2008-05-15 3:13 cron Marc Kirby
2008-05-15 16:27 ` cron Pierre A. Humblet
2007-12-19 18:59 cron Bruno Zovich
2007-12-19 20:51 ` cron Pierre A. Humblet
2007-09-12 14:40 cron Alexander Polson
2007-09-12 14:58 ` cron Larry Hall (Cygwin)
2007-09-13 5:26 ` cron Pierre A. Humblet
2007-09-13 6:00 ` cron René Berber
2007-09-13 15:35 ` cron Pierre A. Humblet
2007-09-13 18:25 ` cron Larry Hall (Cygwin)
2007-08-31 15:25 cron Barry Benowitz
2007-08-31 15:50 ` cron Larry Hall (Cygwin)
2007-08-31 16:34 ` cron Pierre A. Humblet
2007-08-08 14:50 cron Kiran, Shashi
2007-08-08 16:26 ` cron Pierre A. Humblet
2007-08-09 9:44 ` cron shash
2007-04-12 16:07 cron Gary Worthy
2007-04-12 16:15 ` cron Dave Korn
2003-05-09 1:37 cron Bill C Riemers
2003-04-01 17:27 cron! Igor Pechtchanski
2003-04-01 17:32 ` cron adam r. christopher
2003-04-01 17:42 ` cron Igor Pechtchanski
2003-04-01 17:45 ` cron Igor Pechtchanski
2003-04-01 18:37 ` cron Thorsten Kampe
2002-01-07 2:30 cron Facey Brian
2002-01-07 3:46 ` cron Gerrit P. Haase
2001-07-13 13:08 cron David G. Baur
2001-07-13 13:12 ` cron Gerrit P. Haase
2001-06-20 19:32 Cron Bob Zimmerman
2001-06-21 2:22 ` Cron Michael Schaap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6.1.0.6.0.20040511183007.031c4240@127.0.0.1 \
--to=cygwin-lh@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=jhayes@verilet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).