From: upat54wo@aol.com
To: drobinow@dayton.adroit.com, cygwin@cygwin.com
Subject: Re: crontab -e problem
Date: Wed, 26 Jun 2002 12:23:00 -0000 [thread overview]
Message-ID: <31FAEA60.6425E801.00AC0A81@aol.com> (raw)
Thanks for straightening out my thinking, David.
With all the warnings and disclaimers, however, I am uncomfortable with applying the snapshot because it might cause more problems than I need in a production environment. And cron itself is working - driving a very important function every 15 minutes at the moment.
Guess I have to wait for an offical release...
David
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-06-26 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 12:23 upat54wo [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 13:02 upat54wo
2002-06-26 12:29 Elfyn McBratney
2002-06-26 9:47 Robinow, David
2002-06-26 9:39 Elfyn McBratney
2002-06-26 9:39 upat54wo
2002-06-26 8:31 upat54wo
2002-06-26 8:35 ` Corinna Vinschen
2002-06-26 8:56 ` Christopher Faylor
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=31FAEA60.6425E801.00AC0A81@aol.com \
--to=upat54wo@aol.com \
--cc=cygwin@cygwin.com \
--cc=drobinow@dayton.adroit.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).