"Invalid request code "error

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Hi, I am using the following code to get all the files with "#include" in cwd recursively(pls let me know if there is a better way).Whenever I run this code I get the below warnings.Has anyone faced such issue before?

my @grep_includes=`find.exe . -name "*" -print0 | xargs -0 grep -i #in
+clude`;

OUTPUT:-
grep: ./files/tools/boot: Invalid request code
grep: ./files/tools/boot/bin: Invalid request code
grep: ./files/tools/usbdrivers: Invalid request code
grep: ./files/tools/usbdrivers/win7: Invalid request code
grep: ./files/tools/usbdrivers/xp: Invalid request code
[download]

Comment on "Invalid request code "error Download Code

Replies are listed 'Best First'.
Re: "Invalid request code "error by Anonymous Monk on Mar 20, 2011 at 00:48 UTC
That is an error message from the program grep, which is not perl	[reply]
Re^2: "Invalid request code "error by Anonymous Monk on Mar 20, 2011 at 00:56 UTC
The reason I am asking me when I run the below command `"find.exe . -name "*" -print0 \| xargs -0 grep -i #include"` [download] from any command window I dont see the grep error message ,only when I put it in a perl script and run I get this error message.So I thought something to do with perl. Does any one know if there is an yother way to get all the #includes in a given directory recursively?	[reply] [d/l]
Re^3: "Invalid request code "error by Anonymous Monk on Mar 20, 2011 at 03:57 UTC
Can anyone help?	[reply]
Re^4: "Invalid request code "error by Anonymous Monk on Mar 20, 2011 at 04:10 UTC
Re^4: "Invalid request code "error by Anonymous Monk on Mar 20, 2011 at 04:30 UTC
Re^5: "Invalid request code "error by Anonymous Monk on Mar 20, 2011 at 05:00 UTC
Some notes below your chosen depth have not been shown here
Re: "Invalid request code "error by Anonymous Monk on May 23, 2019 at 06:49 UTC
This is what I'm getting when trying to run grep from find on a directory. I can see your case is the same (./files/tools/boot, ./files/tools/boot/bin, ... are dirs). Use "! -type d" clause to filter them out -- or just ignore the warning, it doesn't seem to be harmful. ((NB Sorry for a late answer :-))	[reply]