Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Thorsten Kampe <thorsten AT thorstenkampe DOT de>
Subject: Re: multiple cron cause problem
Date: Tue, 2 Mar 2004 13:53:48 +0100
Lines: 34
Message-ID: <1039zzlhcv03r$.dlg@thorstenkampe.de>
References: <HMEFLKPCFMNCFAHAEGPOCEBECAAA DOT mchen AT coe DOT ubc DOT ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: isi-dialin-129-69.isionline-dialin.de
User-Agent: 40tude_Dialog/2.0.10.1de

* Michael Chen (2004-03-02 12:08 +0100)
> As many users did, cron starts with bash. (probably in .barshrc)

Sorry? Cron is a normal windows service and a look into your .bashrc
would advise you: "grep cron ~/.bashrc". And bash is not the default
shell for cron - if you meant this - but "sh": "man 5 crontab".

> But we keep open new terminal, because of more jobs or previous termial
> deadlock.
> Thus we started many cron process at different time.
> Will this cause problem?

Cron is not started via bash and it doesn't use a terminal.
 
> I observed that cron procedures remain in the windows NT Task Manager even
> after the terminal finish or be throttled.
> Is it supposed to be?

Sorry, but again: cron has nothing to do with your terminal. It
"forks" when it executes a new job and terminates afterwards.
 
> It is also observed that cygwin.bat in the distribution, which uses NT
> termial + bash is worse at terminating cron, while xterm+bash is better at
> cleaning up.

Definetely not as cron is a normal windows service and runs in the
background - so no terminal is involved at all (Windows console, rxvt,
xterm).

I think you have a totally wrong or missing impression of what cron is
and what it does. Please read the manpage of cron and crontab and
/usr/share/doc/Cygwin/cron.README

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/