X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew DeFaria Subject: Re: Automating a Cygwin Script From Windows Date: Fri, 28 Aug 2009 20:02:15 -0700 Lines: 13 Message-ID: References: <25196125 DOT post AT talk DOT nabble DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.23 (X11/20090817) In-Reply-To: <25196125.post@talk.nabble.com> X-Stationery: 0.4.10 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 jprice wrote: > I need to run a cygwin script directly via windows, probably via dos > prompt or some other comparable method. This method needs to be > automated and kicked off in Windows at certain times, so executing > Cygwin, then manually typing in the script to run in the Cygwin prompt > is out of the question. If you merely need to run an executable periodically (IOW at a predetermined time/interval) then why not stay in the Cygwin environment and use cron(1). Just set up cron and then add a cron job to execute you script. -- Andrew DeFaria Old dog still learning - please don't shoot yet -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple