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 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Bash extremely slow when started via task scheduler Date: Thu, 9 Oct 2003 14:26:20 +0200 Message-ID: <06CAA4D3753C53408D2CE6340B68444201D9454B@vbeexc02.emea.cpqcorp.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Pensa, Pascal" To: X-OriginalArrivalTime: 09 Oct 2003 12:26:28.0272 (UTC) FILETIME=[9022F300:01C38E60] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h99CQxpE003583 From: Jason Tishler [mailto:jason AT tishler DOT net] >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'. As workaround I started the script with another bash (to access cygwin /dev/null) , it work just fine now but it's a bit ugly (bash forking bash...) so any better idea will be appreciated: Before: bash myscript Has been replaced by: bash -c "bash myscript >/dev/null