From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Weird behavior in 'grep'ing for string in /proc/registry...
Date: Mon, 7 Sep 2020 22:51:26 +0200 [thread overview]
Message-ID: <20200907205126.GK4127@calimero.vinschen.de> (raw)
In-Reply-To: <ddc33d3b-3caf-447e-fbd1-e53192eb55bc@towo.net>
On Sep 7 09:53, Thomas Wolff wrote:
> Am 07.09.2020 um 09:05 schrieb Brian Inglis:
> > On 2020-09-06 23:34, L A Walsh wrote:
> > > In directory
> > > /proc/registry/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/eventlog
> > > I wanted to list all the ".dll"s that handled various types of
> > > events.
> > >
> > > I tried
> > > /bin/grep -Pr '\.dll'
> > >
> > > but got a load of bogus error messages:
> > >
> > > /bin/grep: Group: Is a directory
> > > /bin/grep: ImagePath: Is a directory
> > > /bin/grep: Description: Is a directory
> > > /bin/grep: ObjectName: Is a directory
> > > ....
> > [...]
> I reproduced Lindas observation (although not in the folder she mentioned
> which does not exist here) and in fact there is an inconsistency between
> `grep -r` reporting "Is a directory" for entries that are not marked as
> directory by `ls`:
> .pwd
> /proc/registry/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Appinfo/Parameters
> .ls -l
> insgesamt 0
> -r--r----- 1 SYSTEM SYSTEM 34 27. Nov 2019 ServiceDll
> -r--r----- 1 SYSTEM SYSTEM 4 27. Nov 2019 ServiceDllUnloadOnStop
> .grep -r .
> grep: ServiceDll: Is a directory
> grep: ServiceDllUnloadOnStop: Is a directory
>
> I checked whether `opendir` marks the d_type fields wrong in the /proc
> filesystem but that's not it.
No, it's a collision of an internal flag with an official open(2) flag
from fcntl.h, used by grep in this case. I changed the way the internal
flag is used so it doesn't collide with fcntl.h flags ever, even if we
add some more.
I uploaded new snapshots for testing to https://cygwin.com/snapshots/
Please give them a try.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
next prev parent reply other threads:[~2020-09-07 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 5:34 L A Walsh
2020-09-07 7:05 ` Brian Inglis
2020-09-07 7:53 ` Thomas Wolff
2020-09-07 19:15 ` Brian Inglis
2020-09-07 20:51 ` Corinna Vinschen [this message]
2020-09-07 21:34 ` cygwin1.dll: uname_x not found L A Walsh
2020-09-08 7:18 ` Corinna Vinschen
2020-09-08 18:28 ` L A Walsh
2020-09-08 18:47 ` Thomas Wolff
2020-09-08 19:21 ` Corinna Vinschen
2020-09-08 19:21 ` Corinna Vinschen
2020-09-08 19:25 ` Corinna Vinschen
2020-09-07 14:02 ` Bug in 'grep'ing for string in /proc/registry L A Walsh
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=20200907205126.GK4127@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).