public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cygwin-help@cygwin.com
To: listarch-cygwin@sourceware.org
Subject: ezmlm warning
Date: Mon, 14 Sep 2009 10:29:00 -0000	[thread overview]
Message-ID: <1252924166.7879.ezmlm-warn@cygwin.com> (raw)

Hi! This is the ezmlm program. I'm managing the
cygwin@cygwin.com mailing list.


Messages to you from the cygwin mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the cygwin mailing list,
without further notice.


I've kept a list of which messages from the cygwin mailing list have 
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
   <cygwin-get.123_145@cygwin.com>

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
   <cygwin-index@cygwin.com>

Here are the message numbers:

   154360

--- Enclosed is a copy of the bounce message I received.

Return-Path: <davidt81@earthlink.net>
Received: (qmail 1925 invoked by uid 22791); 2 Sep 2009 17:41:18 -0000
X-SWARE-Spam-Status: No, hits=-0.5 required=5.0
	tests=AWL,BAYES_00
X-Spam-Status: No, hits=-0.5 required=5.0
	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from elasmtp-scoter.atl.sa.earthlink.net (HELO elasmtp-scoter.atl.sa.earthlink.net) (209.86.89.67)
    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Sep 2009 17:41:08 +0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=uBkfM3lB5G8gmvhVbulvM4OU8yG2UL7NwLQ7s1iJcEbTAK9sKmcfrrF3DMzAjmfC;
  h=Received:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:X-MimeOLE:Message-ID:X-ELNK-Trace:X-Originating-IP;
Received: from [69.86.53.234] (helo=minid)
	by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67)
	(envelope-from <davidt81@earthlink.net>)
	id 1MitpT-0001yz-0v
	for cygwin-return-154360-listarch-cygwin=sourceware.org@cygwin.com; Wed, 02 Sep 2009 13:41:07 -0400
From: "David Tazartes" <davidt81@earthlink.net>
To: <cygwin-return-154360-listarch-cygwin=sourceware.org@cygwin.com>
Subject: Re: Simple bash script is slow to execute - appears to be time spent starting commands like ls
Date: Wed, 2 Sep 2009 13:41:02 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: Acor9IowhH6bCsUmTZCFGGx93XR1UA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
Message-ID: <E1MitpT-0001yz-0v@elasmtp-scoter.atl.sa.earthlink.net>
X-ELNK-Trace: 5bf265d7c89f1e8e1aa676d7e74259b7b3291a7d08dfec79bef146dc33692d298b908557d1707d2b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.86.53.234

Jeremy Bopp wrote:

While I believe the usual forking performance issue is probably the
largest factor for your problem, you *are* running an instance of
Windows Explorer.  It's displaying your desktop which as you indicate
above is holding the folder containing your work area.  My guess is that
you're seeing those usage spikes because of that fact.  Try working in a
tree which is outside of your desktop, maybe in /tmp, and see if that
makes any difference for you.

I can't reproduce the slowness you're seeing in general however, even in
a directory on the desktop, but then I'm running with XP rather than Vista.

-----

I didn't achieve any noticeable speedup, and the echo | cut slowness is
still there irrespective of directory (no surprise since it doesn't touch
any files except /usr/bin/cut). 

What do you say we focus on the echo | cut slowness problem, since it
eliminates lots of variables and is much easier to test.


             reply	other threads:[~2009-09-14 10:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 10:29 cygwin-help [this message]
     [not found] <1557166949.6367.ezmlm-warn@cygwin.com>
2019-05-06 19:04 ` Chris Wagner
2019-05-06 19:26   ` Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2017-08-14  9:22 cygwin-help
2016-11-02 10:43 Andrey ``Bass'' Shcheglov
2016-11-02 13:05 ` Eric Blake
2016-11-02 13:13   ` cyg Simple
2016-11-02 14:52     ` Herbert Stocker
2016-11-02 14:55   ` Jack
2016-11-02 13:05 ` cyg Simple
2015-10-05  9:09 cygwin-help
2010-02-07 14:38 cygwin-help
2005-06-15 16:28 cygwin-help
2004-09-30 11:01 cygwin-help
2004-06-08 16:19 cygwin-help
2001-12-20 23:02 cygwin-help
     [not found] <955193687.11707.ezmlm-warn@sourceware.cygnus.com>
2000-04-10  1:08 ` Don Sharp
2000-04-10 10:15   ` Chris Faylor
     [not found]     ` <006301bfa32a$cbeeec10$5f0f4dd1@TIMYX18EWDT6RQ>
2000-04-10 13:36       ` Chris Faylor
2000-04-10 13:44         ` Jeff Sturm
2001-04-16  6:30     ` Chris Faylor
2001-09-04 23:46     ` Chris Faylor
2001-09-05  4:06     ` Don Sharp
     [not found]   ` <38F1E5D0.262ED39B@sigma6.com>
2000-04-11  1:07     ` Don Sharp
     [not found]   ` <200004101712.NAA09157@rtl.cygnus.com>
2000-04-11  1:17     ` Don Sharp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1252924166.7879.ezmlm-warn@cygwin.com \
    --to=cygwin-help@cygwin.com \
    --cc=listarch-cygwin@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).