Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
10
Newest
 Cleanup
Impact
~4k people reached

  • 0 posts edited
  • 0 helpful flags
  • 6 votes cast
Apr
4
comment How do I use man pages to learn how to use commands?
I'd answer, but I'm afraid you wouldn't read it all...
Feb
18
revised Remove duplicate $PATH entries with awk command
rolled back to a previous revision
Feb
18
awarded  Cleanup
Feb
18
revised Remove duplicate $PATH entries with awk command
rolled back to a previous revision
Oct
6
awarded  Teacher
Sep
24
awarded  Autobiographer
Jun
11
awarded  Popular Question
Apr
18
comment Best way to determine piped command to shell script?
Yes, I think you and Glenn Jackman are both correct. Thinking it wasn't possible was the first conclusion I came to, but I don't consider myself a Linux guru. I had hope that the Kernel might pass that information along in some way, so scripts could behave differently based on origination of STDIN -- logging was just one of the many potential uses.
Apr
17
comment Best way to determine piped command to shell script?
@glennjackman right. Exactly my line of thinking, which is why I'm looking for the best way. Preference would be not to quote. I'd rather sniff the shell history (if it's available at that point)
Apr
17
revised Best way to determine piped command to shell script?
edited tags
Apr
17
comment Best way to determine piped command to shell script?
print.sh will log the input, as well as format/output as part of a custom header
Apr
17
asked Best way to determine piped command to shell script?
Aug
13
awarded  Popular Question
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Kevin: then that makes sense (thank you), I was talking about the combination of them both, which I don't know how it'd work, but I imagine it could check the same file exponentially
Oct
25
awarded  Editor
Oct
25
revised Linux: Does find | xargs grep have limitations?
Fixed grammar
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Kevin: I think I misunderstood you. Were you talking about using grep as a standalone instead of piping find's output to it?
Oct
25
comment Linux: Does find | xargs grep have limitations?
that's a valid comment and I tried to answer it with I realize I wasn't specific on the path, but these are all well-named directories, not to be confused with any devices. It's still possible that a malformed filename with spaces could have split oddly - I'll have to check when I have a little more time; however I doubt it. I typically don't use spaces in Linux. I think in looking at the "errors" the stopping point was at different places, but like I said... I will check because I hate not knowing the cause of problems to prevent them in the future.
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Kevin: I'm not sure what that would buy me. find is supplying all the files, so grep shouldn't also need to read each file twice; unless, I'm not understanding the recursive nature of grep
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Gilles: before I post a question, I try many options. In this particular instance it had no bearing on the outcome, so I included the version as part of the question