Shell Programming and Scripting

I just need to get the server back working again! The old grep command I used at least worked then....

---------- Post updated at 07:41 AM ---------- Previous update was at 07:36 AM ----------

Windows NT

---------- Post updated at 07:44 AM ---------- Previous update was at 07:41 AM ----------

I ran the find part of the statement & it work. Then I ran the grep part & it still works. But it won't work together as it use to run! I don't understand!

---------- Post updated at 07:45 AM ---------- Previous update was at 07:44 AM ----------

It keeps coming back with no data. But when I do an

Code:

ls or grep -l "Status" *.xml

They're there! I'm confused! Help! lol Please?

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 it fromthe task manager.


Please explain in detail and plain English what your problems are, also supplying input and desired output samples.

I've only got today to get it running like it use too!

---------- Post updated at 08:01 AM ---------- Previous update was at 07:50 AM ----------

Ok when I changed my find . -name "*.xml" -exec grep -l "Status" {} \; to

Code:

uname -a
xmlFileNames=$(find . -name "*.xml" -exec grep -Fl "Status" {} '+')
printf "find w/ grep -F exit code: %d\n" $?
xmlFileNames=$(find . -name "*.xml" -exec fgrep -l "Status" {} '+')
printf "find w/ fgrep exit code: %d\n" $?

I got this error message.

Code:

find: non-terminated '-exec' argument list
Usage: find directory ... expression
find w/ grep -F exit code:2 
find: non-terminated "-exec' argument list
Usuage: find directory ... expression
find w/ fgrep exit code: 2

And now ever since then I haven't been able to run my script or the earlier find command from the command line. I don't know what to do...

---------- Post updated at 08:05 AM ---------- Previous update was at 08:01 AM ----------

I tried

Code:

which find

Because I thought maybe it was pointing at the wrong file for the find command. But It's pointing at the mks tool kit...I've triple checked my syntax over. And that's not it. Plus the script use to run. Yeah it took a while but it ran. Now it runs but can't find any of the files. I did an

Code:

ls

&

Code:

grep -l "status" *.xml

right after the script came back with no data. And the files are right there.

---------- Post updated at 08:19 AM ---------- Previous update was at 08:05 AM ----------

Somebody please help me? I have learned a valuable lesson from all of this! Learn my commands before using them!

---------- Post updated at 08:37 AM ---------- Previous update was at 08:19 AM ----------

Well, I've restarted the server & still the same problem!

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 first lines. Then use grep status on that .xml file. Report back.

Yes the status is in the first line of the xml files.

---------- Post updated at 09:05 AM ---------- Previous update was at 09:04 AM ----------

And the grep did work from the command line.

OK. What's the problem now?

The find part works too from the command line. The just wont work when I put them together.

Code:

xmlFileNames=$(find . -name "*.xml" -exec grep -l "Status" {} \; 2>/dev/null)

IDK why? I even took off the /dev/null/ part...