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
From:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: tcsh terminate unexpectedly
Date:	Tue, 20 Jul 2004 10:15:35 +0100
MIME-Version:	1.0
In-reply-to:	<20040719202548.QVGU2023.mta9.adelphia.net@mail.adelphia.net>
Message-ID:	<NUTMEG9B0kY8fNp0Vat0000095a@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	20 Jul 2004 09:15:35.0375 (UTC) FILETIME=[1D684DF0:01C46E3A]

> -----Original Message-----
> From: cygwin-owner On Behalf Of bobmills1
> Sent: 19 July 2004 21:26

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

  Different username?  Different permissions and access rights?  Lack of the
INTERACTIVE group in the logon token?  There are various environmental
factors that differ when you run something from the scheduler rather than
from the command line as the logged on user.

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

  Sprinkle it full of lines that say

echo Still alive here! >> /scriptlog.txt

and then see how far it gets through them to identify the failing command.

  Or perhaps, just get the scheduler to launch a tcsh shell, then run the
script manually from that; it should still fail in the same way.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -