Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: Subject: RE: Cron problem/Documentation and Setup Date: Wed, 18 Aug 2004 17:01:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 18 Aug 2004 16:01:10.0828 (UTC) FILETIME=[94727EC0:01C4853C] > -----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.... 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? 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/