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 To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Andrew DeFaria Subject: Re: cron problem in W2K Proffesional Date: Mon, 09 Dec 2002 16:58:05 -0800 Lines: 29 Message-ID: <3DF53C1D.3080404@Salira.com> References: <20021207014022 DOT 35565 DOT qmail AT web21406 DOT mail DOT yahoo DOT com> NNTP-Posting-Host: 206.184.204.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1039481985 7118 206.184.204.2 (10 Dec 2002 00:59:45 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Tue, 10 Dec 2002 00:59:45 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en, ru, zh Eric De La Cruz Lugo wrote: > The cron works now!, the output its ok (date.txt). > > but with my script the things are different, here are > the files I use.. I tested the script from the command > line and work flawlesly, but when i add it to my > crontab it does not work has expected! > > the files are atached to the mail, and the output from > the script being executed by the cron its there too. > > hope you can help me or advise me. My suspicion would be that somewhere along the line you are referencing a mount point or a mapped location that just is not accessible from cron. Cron's environment does not insure that all network locations are accessible. I remember asking about this in the past. There is some difference between mount points where some are "global" and some are not. IIRC I never got a satisfactory answer as to the question of how one tells the difference. You should probably add some cron entries to ls various files you depend on using their exact paths that you use in your scripts. One of them will most likely fail. Meantime you might want to set up SMTP so that cron can email you when you make typos like /usr/sbin/date... :-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/