Re: bug found from ls command

[PG]

ah, great!

thank you for the info. That helps me understand a lot. Now I see why find
fails. And perhaps it's not worth the extra computation time required to,
upon failure of cd'ing into the directory, trying to list it.

I still think there should be an option for find that one could turn on that
would do everything possible to find a certain filename.

Thanks for the explanations.

2009/7/7 Philip Rowlands 

> On Mon, 6 Jul 2009, PG wrote:
>
>  r...@system76-pc:/home/xinwei/bugreport# ls -l
>> total 4
>> d---r--r-- 2 root root 4096 2009-07-05 13:27 protected
>>
>
>  xin...@system76-pc:~/bugreport$ ls -l protected/
>> ls: cannot access protected/canttouchthis: Permission denied
>> total 0
>> -? ? ? ? ?? canttouchthis
>>
>
> http://www.gnu.org/software/coreutils/manual/html_node/Mode-Structure.html
> ---
>   There are three kinds of permissions that a user can have for a file:
>
>  1. permission to read the file.  For directories, this means
> permission to list the contents of the directory.
> ---
>
> A directory with "read" permission allows the directory to be listed. This
> is not a bug.
>
>
>  xin...@system76-pc:~/bugreport$ find ./ -name canttouchthis
>>
>
> Curiously I get a different error here:
>
> $ find ./ -name canttouchthis
> find: ./protected: Permission denied
>
> In theory find could show the file, but it attempts to chdir into the
> directory before listing, which is not allowed by the directory permissions.
>
>
> Cheers,
> Phil
>
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils

bug found from ls command

[PG]

Dear coreutils,

Actually, I'm not sure if ls is the perpetrator, but maybe you guys can find
out where things go wrong. I do not think that the filename "canttouchthis"
should be listed when I am not root in the following situation:

r...@system76-pc:/home/xinwei/bugreport# ls -l
total 4
d---r--r-- 2 root root 4096 2009-07-05 13:27 protected
r...@system76-pc:/home/xinwei/bugreport# ls -l protected
total 0
-rw-r--r-- 1 xinwei xinwei 0 2009-07-05 13:27 canttouchthis
r...@system76-pc:/home/xinwei/bugreport# exit
xin...@system76-pc:~/bugreport$ ls -l protected/
ls: cannot access protected/canttouchthis: Permission denied
total 0
-? ? ? ? ?? canttouchthis
xin...@system76-pc:~/bugreport$ find ./ -name canttouchthis
xin...@system76-pc:~/bugreport$ sudo !!
sudo find ./ -name canttouchthis
./protected/canttouchthis
xin...@system76-pc:~/bugreport$


Thanks!
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils

Filename pattern in grep --include=....

[Com MN PG P E B Consultant 3]

>From the grep man-page:

   --include=PATTERN
  Recurse in directories only searching file matching
PATTERN.

What type of PATTERN can be used here (i.e. glob, regex, extended regex,
etc.)?

For example, I want to search recursively below a directory D, but want
to check
only files starting with "no" or "uh". How do I do this using --include
?

I tried the following:

  # glob pattern
  grep -r --include="{no,uh}*" abc D

and the following:

  # extended regexp
  grep -r --include="(no|uh).*" abc D

but neither variant located my files. But I know that there are files
matching, because

  # Look at all files
  grep -r abc D

shows some matching files starting with 'no' and 'uh'.

Ronald
-- 
Ronald Fischer (phone +49-89-63676431)
mailto:[EMAIL PROTECTED]


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils