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 Date: Thu, 13 Feb 2003 22:42:16 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Problem in Cron job setup in cywin 1.1.8 on windows NT machine Message-ID: <20030214034216.GB3687@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <005501c2d3d7$5256e110$ab7886d9 AT webdev> <00ec01c2d3d8$1b9c4ce0$412e0b93 AT ALAGraman1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ec01c2d3d8$1b9c4ce0$412e0b93@ALAGraman1> User-Agent: Mutt/1.5.1i On Thu, Feb 13, 2003 at 07:21:03PM -0800, Geetha Raman wrote: >I didn't upgrade cygwin because some of our script are compatible to run >with newer version and we are happy with the version we have. Well, then, you are out of luck. Time marches forward and you're stuck in the past. Please don't waste *our* time by updating a package, expecting it to work with a two year old version of the cygwin DLL, and then asking us how to fix this problem for you when it doesn't. It should be very obvious from the error message that you received that this isn't going to work. >and I just downloaded the package related to cron and cygrunsrv to >setup a cron functionality in my windows machines so that i need not >have to manually start the script file every time. Using the bunzip2 >and tar command i installed it on top of the old installation >directory. I rebooted the machine today morning. Urk. cgf -- 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/