Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
X-Originating-IP: [24.140.0.122]
From: <bobmills1 AT adelphia DOT net>
To: <cygwin AT cygwin DOT com>
Subject: tcsh terminate unexpectedly
Date: Mon, 19 Jul 2004 16:25:48 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20040719202548.QVGU2023.mta9.adelphia.net@mail.adelphia.net>

I'm running cygwin on a WIN2k server and have the following trouble with a tcsh executable script.

*When run from an login shell (tcsh -l) the script runs without error.

*I recently attempted to run the script from the WIN scheduler and the script terminated unexpectedly. The Properties of the shortcut program used in the scheduler was "tcsh name_of_script".

*The script always terminates at the same point so it is not a random error.

My questions are;
1. Why would a script that runs normally when run 
   interactively, terminate
   when run in the scheduler.
2. What would be the best way to debug (tcsh -xn     
   name_of_script)?
   Because is shuts down unexpectedly and the shell 
   disappears these techniques would be difficult to     
   utilize.

Bob Mills
Engineering Services Manager
Akron Brass Company



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