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: Cron problem/Documentation and Setup
Date:	Wed, 18 Aug 2004 17:51:11 +0100
MIME-Version:	1.0
In-Reply-To:	<Pine.GSO.4.61.0408181215220.1878@slinky.cs.nyu.edu>
Message-ID:	<NUTMEGf69aZbLAX3cf300000e27@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	18 Aug 2004 16:51:11.0796 (UTC) FILETIME=[9129DF40:01C48543]

> -----Original Message-----
> From: Igor Pechtchanski
> Sent: 18 August 2004 17:19

> On Wed, 18 Aug 2004, Dave Korn wrote:
> 
> > > -----Original Message-----
> > > From: cygwin-owner On Behalf Of Igor Pechtchanski
> > > Sent: 18 August 2004 16:54
> > 
> > > > > > 18 17 * * * pwd >> /tmp/debug.log 2>&1
> > > > > > 19 17 * * * ls >> /tmp/debug.log 2>&1
> > > > > > 20 17 * * * ls -l /tmp/myscript >> /tmp/debug.log 2>&1
> > > > > > 21 17 * * * /tmp/myscript >> /tmp/debug.log 2>&1
> > 
> > > 19 17 * * * ls >> /tmp/debug.log 2>&1
> > > 20 17 * * * ls -l /tmp/myscript >> /tmp/debug.log 2>&1
> > 
> >   I haven't been following, so PMFBI, but can I just point 
> out that it may
> > well be necessary that the 2>&1 should precede the >> 
> /tmp/debug.log if you
> > want stderr to actually end up in the log file....
> 
> Nope, that part was correct.  If you put 2>&1 before the >> 
> redirection, 
> stderr will end up on stdout.  See the sh and bash manpages.

  My bad.  GOK how I managed to misremember that, but I was sooo certain
that I'd had to painfully discover that they needed to be the other way
round myself once.  Guess I must have discovered it the way round you've got
it, after all.  I just tested redirection under cmd.exe and even that
behaves the same way, so I didn't even get it from M$-world.  Pardon my
confabulation.

> >   BTW, "uname -a; pwd; set; export" might be a good 
> diagnostic command to
> > add as a cron job.... isn't this almost certainly a
> > wrong-user-executing-the-job problem?
> 
> Huh?  "uname -a" should only be useful if there's more than 
> one Cygwin 
> version on the machine -- otherwise, the output should be 
> identical for 
> all users.  "pwd" is already there.  I don't see how "set;export;" is 
> relevant at all, frankly...  Did you, by chance, mean "id" instead?

  I meant "id" rather than uname, yes.  As for "set; export", I don't see
how you can consider the execution environment to _not_ be relevant; it's
full of useful and even vital diagnostic information, such as $PATH, to name
but one....

    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 -