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 From: "Chris January" To: "Cygwin@Cygwin.Com" Subject: RE: Bash extremely slow when started via task scheduler Date: Thu, 9 Oct 2003 17:32:49 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-reply-to: <06CAA4D3753C53408D2CE6340B68444201D9454B@vbeexc02.emea.cpqcorp.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > >Why not use cron instead? > > > >Jason > > Thank you for suggestion but it's an application server managed by > non-UNIX 'mouse users' which may manually start the task, so it should > be simple for them. > > It seems that not having an output window slows down the script > dramatically on each 'echo'. I assume you are using Windows 2000? Could it be that Cygwin is waiting for the caption of the console window to change, but it never does because it's on a hidden desktop? Chris -- 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/