From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: cygwin@cygwin.com
Subject: Re: cron dying in Windows but not in Cygwin
Date: Thu, 27 May 2004 13:25:00 -0000 [thread overview]
Message-ID: <15uzhz9jogd14.dlg@thorstenkampe.de> (raw)
In-Reply-To: <NUTMEGQWlD3TQeNKzfk00000089@NUTMEG.CAM.ARTIMI.COM>
* Dave Korn (2004-05-27 11:26 +0100)
>> * Robert Pollard (2004-05-26 18:33 +0100)
>>> I have a bit of a problem where when we launch cron from
>> the command
>>> line after a few days it dies in Windows but is still visible in
>>> Cygwin.
>>
>> Beg your pardon? Your sentence doesn't make sense to me.
>>
>>> Currently, I run a script that launches /usr/sbin/cron. This
>>> script only launches cron if it isn't running.
>>>
>>> Does it have something to do with not launching from an rc file?
>>
>> Excuse me? rc files are /configuration/ files...
>
> Have you ever actually *read* one? They're shell scripts.
You mean the runlevel scripts in rc.d? They're neither part of the
default Cygwin nor of cron installation so I didn't think of these.
/I/ meant "rc files" like bashrc, zshrc, etc.
This misunderstanding proves only two things:
1. People who are retentive with facts and descriptions (like RP)
provoke misunderstandings inevitably.
2. If RP had even a slight understanding of Cygwin, he would have
known that no "runlevel script" is required to start a "Cygwin
service/daemon" (because there are no Cygwin services or daemons; just
Windows services.)
But I'm not even sure that RP read the cron readme so 2. may be
pointless.
Thorsten
--
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-27 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 17:48 Robert Pollard
2004-05-26 19:59 ` Dave Korn
2004-05-27 0:17 ` Thorsten Kampe
2004-05-27 9:55 ` Dave Korn
2004-05-27 13:25 ` Thorsten Kampe [this message]
2004-05-27 13:36 ` Vince Hoffman
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=15uzhz9jogd14.dlg@thorstenkampe.de \
--to=thorsten@thorstenkampe.de \
--cc=cygwin@cygwin.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).