From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16090 invoked by alias); 26 Sep 2003 15:38:44 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 16083 invoked from network); 26 Sep 2003 15:38:43 -0000 Received: from unknown (HELO mail.broadpark.no) (217.13.4.2) by sources.redhat.com with SMTP; 26 Sep 2003 15:38:43 -0000 Received: from pest (217-13-20-38.dd.nextgentel.com [217.13.20.38]) by mail.broadpark.no (Postfix) with SMTP id C9CAE78DB5 for ; Fri, 26 Sep 2003 17:38:42 +0200 (MEST) From: =?iso-8859-1?Q?=D8yvind_Harboe?= To: Subject: cron problems finally resolved Date: Fri, 26 Sep 2003 15:43:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-09/txt/msg01697.txt.bz2 After much knashing of teeth, I've finally figured out what made my cron scripts fail: In a normal shell, the /usr/bin is in at the front of the $PATH. When cron runs as a cygrunsrv service /usr/bin is at the end of the $PATH. In my case, I had a Windows version of "tar" that being executed instead of CygWins "tar", but only when run from within cron as a service. My workaround was to launch the subcript in question via "bash": bash --login -i -c "sh /cygdrive/c/foo/backup.sh" This is not the first time I've run into $PATH problems between Windows and CygWin. Something to look out for. Øyvind -- 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/