X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: "'The Cygwin Mailing List'" References: <042e01c85671$6aa39de0$0a00a8c0@a64x23800p> <009001c8572b$71b77d80$0a00a8c0@a64x23800p> Subject: RE: Running perl script in cron in cygwin under Windows Date: Wed, 16 Jan 2008 18:49:31 -0000 Message-ID: <000501c85870$88157c30$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <009001c8572b$71b77d80$0a00a8c0@a64x23800p> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com >> Cron works on other scripts but not with a perl script. If it's the >> environment (we are running korn instead of the bash default), it >> might be good to create a wrapper script in korn shell. perl often needs a rebaseall run to function at its best. >> Does cron use bash default profile for the login to run? That could >> be the key. > > It's also been a while since I had to solve cron problems, but I believe > cron doesn't use any shell -- it just launches whatever program and > arguments you feed it (via one of the exec() calls?). So if you want to run > shells, scripts, etc., you have to do whatever set up your code expects. See also "cron_diagnose.sh" and /usr/bin/cron-config. 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/