Search Results

OK. Build a sandbox, create dummy xml files with "Status" in their first line, and then run the respective commands. Experiment with parameters. Use commands with whole absolute paths. Come back with...

It did the ls -la but it didn't do the grep. Sure there is "status" in it? Please post first lines.

You are using "Status" and "status" interchangingly. You know that *nix is case sensitive?

Sorry, I don't quite get what you are saying. You are always talking generically, no data, no details. How then do you expect somebody to help you?
What variable? What script? What environment?...

It's not easy to analyse what you say. So - find -exec ls -la {} \; did succeed; it listed the relevant files. Now tryfind . -name "ONE.xml" -exec ls -la {} \; -exec grep -l "status" {} \;
give it...

OK, try thisfind . -name "*.xml" -lsand find . -name "*.xml" -exec ls -la {} \;

Why don't you post command AND error message?

What does your find man page say?

This is what I get for above command:find . -name file\* -exec grep -l 105 {} \;
./file
, so I don't think what you say is correct.

Your "Status" is upper case as opposed to lower in post#24.
Try to run the command without assigning the result to a variable.

OK. What's the problem now?

OK, calm down.
Does the modification date of your .xml files indicate they've been overwritten lately?
Use an editor to open one of the .xml file and look if there's "status" in one of the eight...

We don't know what your server problems are. If it stopped working, that will definitely not be due to those commands.
Or is it just your terminal session that hangs? Try <CTRL>C or <CTRL>D or kill...

Chubler_XL already proposed a solution to overcome that problem.

My comment is just for that command / pipe. No need to restart the server.

You should be careful with NR>8 as it might quit before working on subsequent files.

EDIT: Not even sure if quitting after FNR>8 would be safe...