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
Date: Tue, 02 Mar 2004 03:08:53 -0800
From: Michael Chen <mchen AT coe DOT ubc DOT ca>
Subject: multiple cron cause problem
To: cygwin AT cygwin DOT com
Message-id: <HMEFLKPCFMNCFAHAEGPOCEBECAAA.mchen@coe.ubc.ca>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-IsSubscribed: yes

Dear all,

As many users did, cron starts with bash. (probably in .barshrc)
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?

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?

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.

Any ideas?

Michael Chen


--
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/