Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Message-ID: <430F33F5.3BBBC098@opgc.univ-bpclermont.fr> Date: Fri, 26 Aug 2005 17:23:33 +0200 From: Jean-Michel Douchain MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: crontab References: <430B3DCD.857CD22E@opgc.univ-bpclermont.fr> <430DE5CC.9A9A3629@opgc.univ-bpclermont.fr> <430F1B23.EA7DA18@opgc.univ-bpclermont.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Ah, that may explain it. Is G: a network drive?" That's right. It's a Dos network drive, and in fact, the response of "ls" is very long. I installed cygwin for all users. So I don't know how to manage because my script works by hand!! What are the differents between the cron and the handy execution?? Perhaps including a loop to wait for the answer, will solve my bug?? "You should also look in the Windows Event Log" it looks good, cron started... -- 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/