From: "Dan Higgins" <DanHiggins@austin.rr.com>
To: "Randall R Schulz" <rrschulz@cris.com>, <cygwin@cygwin.com>
Subject: RE: Broken since 1.3.10, or earlier
Date: Tue, 16 Jul 2002 18:30:00 -0000 [thread overview]
Message-ID: <ACEIKCIGAEOGOHGPJPIAIEBLCDAA.DanHiggins@austin.rr.com> (raw)
In-Reply-To: <5.1.0.14.2.20020716164508.02e9fc30@pop3.cris.com>
Ah, it has been a few *years* since I checked the grep man page. Who
would've thought, someone has been improving it all that time... :)
Thanks for the excellent response.
Cheers,
-Dan
Austin, TX, USA
> -----Original Message-----
> From: Randall R Schulz [mailto:rrschulz@cris.com]
> Sent: Tuesday, July 16, 2002 7:01 PM
> To: dan@danamis.com; cygwin@cygwin.com
> Subject: Re: Broken since 1.3.10, or earlier
>
>
> Dan,
>
> I take it that by "inconsistent" you mean the relative ordering of the
> output of the "grep" processes and of the "echo" commands is not
> the strict
> alternation you'd expect.
>
> That's what I see, anyway. I even saw two lines of grep output
> that follow
> the shell prompt printed after the command "completes."
>
> It seems there's some asynchrony in the processing of the output and that
> somehow, in effect, there's a race condition.
>
> I believe we've seen other reports of similar problems.
>
> Someone who knows about the internal architecture of I/O processing in
> Cygwin might be able to shed some light on this. If, for example, there's
> some kind of queuing of I/O operations in Cygwin1.dll between the
> application code (grep or a shell, in this case) and the Windows I/O
> primitives, then there might be an opportunity for this kind of
> asynchrony.
>
> It's too bad strace cannot solve this one, but since there's the
> shell plus
> one grep for each file to be examined, it's not going to help resolve
> relative timing issues.
>
>
> Lest you think this is just idle speculation ... Well it is ...
> But here's
> a concrete suggestion on a work-around:
>
> grep -R --include='*.java' Copyright .
>
>
> If you need those other lines interleaved with the just file
> names, you can
> do this:
>
> (grep -R --include='*.java' Copyright tau rrs;
> grep -l -R --include='*.java' Copyright tau rrs) |sort
>
> This may do everything twice, but on Cygwin, anyway, it's
> distinctly faster
> than your original, what with it's repeated invocation of grep.
>
> I hope you find that helpful.
>
>
> Randall Schulz
> Mountain View, CA USA
[...]
--
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/
next prev parent reply other threads:[~2002-07-17 0:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 18:15 Dan Higgins
2002-07-16 18:23 ` Randall R Schulz
2002-07-16 18:30 ` Dan Higgins [this message]
2002-07-16 18:39 ` Dan Higgins
2002-07-16 20:12 ` Christopher Faylor
2002-07-16 20:38 ` Jon Cast
2002-07-16 21:02 ` Christopher Faylor
2002-07-16 22:16 ` Jon Cast
2002-07-17 5:47 ` egor duda
2002-07-17 6:57 ` Christopher Faylor
2002-07-16 18:32 ` Dario Alcocer
2002-07-16 23:17 ` Andrew DeFaria
2002-07-17 12:31 ` Dan Higgins
2002-07-17 12:52 ` Bernard A Badger
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=ACEIKCIGAEOGOHGPJPIAIEBLCDAA.DanHiggins@austin.rr.com \
--to=danhiggins@austin.rr.com \
--cc=cygwin@cygwin.com \
--cc=dan@danamis.com \
--cc=rrschulz@cris.com \
/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).