Printing inode info from grep

up vote
0
down vote

favorite

I'm currently learning Linux, and some of the practice I've has me absolutely stumped.
I'm trying to look for a file in the current directory with particular text, and output its inode number.
I can confidently do all these things individually but it keeps falling apart when I try to put them together;

 find. -maxdepth 1 -type f | grep -r "#include" -ls -i

but for some reason it just outputs the file names?

Any ideas?

asked Oct 28 '17 at 8:16

StarLord

migrated from stackoverflow.com Oct 29 '17 at 12:56

This question came from our site for professional and enthusiast programmers.

Would find . -maxdepth 1 -type f | grep -r "#include" | ls -i bring you any closer to what you are looking for?
â€“Â arkascha
Oct 28 '17 at 8:28

add a commentÂ |Â

up vote
0
down vote

favorite

 find. -maxdepth 1 -type f | grep -r "#include" -ls -i

but for some reason it just outputs the file names?

Any ideas?

asked Oct 28 '17 at 8:16

StarLord

migrated from stackoverflow.com Oct 29 '17 at 12:56

This question came from our site for professional and enthusiast programmers.

Would find . -maxdepth 1 -type f | grep -r "#include" | ls -i bring you any closer to what you are looking for?
â€“Â arkascha
Oct 28 '17 at 8:28

add a commentÂ |Â

up vote
0
down vote

favorite

 find. -maxdepth 1 -type f | grep -r "#include" -ls -i

but for some reason it just outputs the file names?

Any ideas?

asked Oct 28 '17 at 8:16

StarLord

 find. -maxdepth 1 -type f | grep -r "#include" -ls -i

but for some reason it just outputs the file names?

Any ideas?

asked Oct 28 '17 at 8:16

StarLord

asked Oct 28 '17 at 8:16

StarLord

asked Oct 28 '17 at 8:16

StarLord

asked Oct 28 '17 at 8:16

StarLord

migrated from stackoverflow.com Oct 29 '17 at 12:56

This question came from our site for professional and enthusiast programmers.

migrated from stackoverflow.com Oct 29 '17 at 12:56

This question came from our site for professional and enthusiast programmers.

Would find . -maxdepth 1 -type f | grep -r "#include" | ls -i bring you any closer to what you are looking for?
â€“Â arkascha
Oct 28 '17 at 8:28

add a commentÂ |Â

Would find . -maxdepth 1 -type f | grep -r "#include" | ls -i bring you any closer to what you are looking for?
â€“Â arkascha
Oct 28 '17 at 8:28

Would find . -maxdepth 1 -type f | grep -r "#include" | ls -i bring you any closer to what you are looking for?
â€“Â arkascha
Oct 28 '17 at 8:28

add a commentÂ |Â

2 Answers
2

active

oldest

votes

up vote
2
down vote

find . -type f -exec grep '#include' ; -printf '%p %in'

or grep -q to hide grep output

find . -type f -exec grep -q '#include' ; -printf '%p %in'

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

add a commentÂ |Â

up vote
1
down vote

If you are using grep in recursive mode -r - you don't actually need find command:

grep + xargs approach:

grep -rl '#include' | xargs -I ls -i ''

An approximate output (<inode> <filename>):

1837827 test/1.pdb
1712970 2_clean.pdb
1837846 test2/2.pdb
1712965 1_clean.pdb

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

I assume that grep requires a filename or data via stdin.
â€“Â Cyrus
Oct 28 '17 at 9:45

@Cyrus, explain your phrase
â€“Â RomanPerekhrest
Oct 28 '17 at 9:46

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f401219%2fprinting-inode-info-from-grep%23new-answer', 'question_page');

);

Post as a guest

Name

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

up vote
2
down vote

find . -type f -exec grep '#include' ; -printf '%p %in'

or grep -q to hide grep output

find . -type f -exec grep -q '#include' ; -printf '%p %in'

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

add a commentÂ |Â

up vote
2
down vote

find . -type f -exec grep '#include' ; -printf '%p %in'

or grep -q to hide grep output

find . -type f -exec grep -q '#include' ; -printf '%p %in'

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

add a commentÂ |Â

up vote
2
down vote

find . -type f -exec grep '#include' ; -printf '%p %in'

or grep -q to hide grep output

find . -type f -exec grep -q '#include' ; -printf '%p %in'

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

find . -type f -exec grep '#include' ; -printf '%p %in'

or grep -q to hide grep output

find . -type f -exec grep -q '#include' ; -printf '%p %in'

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

answered Oct 28 '17 at 9:17

Nahuel Fouilleul

1,06667

add a commentÂ |Â

up vote
1
down vote

If you are using grep in recursive mode -r - you don't actually need find command:

grep + xargs approach:

grep -rl '#include' | xargs -I ls -i ''

An approximate output (<inode> <filename>):

1837827 test/1.pdb
1712970 2_clean.pdb
1837846 test2/2.pdb
1712965 1_clean.pdb

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

I assume that grep requires a filename or data via stdin.
â€“Â Cyrus
Oct 28 '17 at 9:45

@Cyrus, explain your phrase
â€“Â RomanPerekhrest
Oct 28 '17 at 9:46

add a commentÂ |Â

up vote
1
down vote

If you are using grep in recursive mode -r - you don't actually need find command:

grep + xargs approach:

grep -rl '#include' | xargs -I ls -i ''

An approximate output (<inode> <filename>):

1837827 test/1.pdb
1712970 2_clean.pdb
1837846 test2/2.pdb
1712965 1_clean.pdb

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

I assume that grep requires a filename or data via stdin.
â€“Â Cyrus
Oct 28 '17 at 9:45

@Cyrus, explain your phrase
â€“Â RomanPerekhrest
Oct 28 '17 at 9:46

add a commentÂ |Â

up vote
1
down vote

If you are using grep in recursive mode -r - you don't actually need find command:

grep + xargs approach:

grep -rl '#include' | xargs -I ls -i ''

An approximate output (<inode> <filename>):

1837827 test/1.pdb
1712970 2_clean.pdb
1837846 test2/2.pdb
1712965 1_clean.pdb

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

If you are using grep in recursive mode -r - you don't actually need find command:

grep + xargs approach:

grep -rl '#include' | xargs -I ls -i ''

An approximate output (<inode> <filename>):

1837827 test/1.pdb
1712970 2_clean.pdb
1837846 test2/2.pdb
1712965 1_clean.pdb

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

answered Oct 28 '17 at 9:19

RomanPerekhrest

22.5k12145

I assume that grep requires a filename or data via stdin.
â€“Â Cyrus
Oct 28 '17 at 9:45

@Cyrus, explain your phrase
â€“Â RomanPerekhrest
Oct 28 '17 at 9:46

add a commentÂ |Â

I assume that grep requires a filename or data via stdin.
â€“Â Cyrus
Oct 28 '17 at 9:45

@Cyrus, explain your phrase
â€“Â RomanPerekhrest
Oct 28 '17 at 9:46

I assume that grep requires a filename or data via stdin.
â€“Â Cyrus
Oct 28 '17 at 9:45

@Cyrus, explain your phrase
â€“Â RomanPerekhrest
Oct 28 '17 at 9:46

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

0F dHp5a3C,lO2j28oWd2JQ,qLkLJ6XqGi WJ oWs8f VLEpyrXMhBrCe35KpRV 0xFGf96obmgTDuV,bNjUXQmM smHrca

搜尋此網誌

mjhjmtu