Please look into the script

#!/bin/bash

path1="/home/backup/newlogs/logs"
path2="/home/backup/softwares/mylogs/logs/"

echo "listing files"

find $path1/server.log.* -type f -mtime +90 -exec ls -lht {} \;
sleep 3
find $path2/server.log.* -type f -mtime +90 -exec ls -lht {} \;

echo "files listed"

exit
---------------------------------------------------------------
problem is that i can list only path1 files. iam unable to list path2 files.

Can anybody please correct this script.

Hi looks good unless there are no files to list in path 2, why don't you try below simple debugging

echo "listing files"

find $path1/server.log.* -type f -mtime +90 -exec ls -lht {} \;
sleep 3

echo "listing path 2"
find $path2/server.log.* -type f -mtime +90 -exec ls -lht {} \;

echo "files listed"

And check the file format

U did no corrections. please correct the script.

In my signature is a link to my blog entry on BASH programming where I show how to do some debug steps for your scripts, My Bash Blog.

One technique is to echo variable values, or echo progress, as you are doing. Another technique is to add the line: near the top of your script, but after the #!/bin/sh line. This will enable verbose debugging and you'll see the progress of the script as well as more details. Give the blog a look for other recommendations.

Note that only you know the full requirements and what you're trying to achieve, and therefore you should evaluate and test with the whole variety of expected conditions that you can conceive of.

For me I would take the mtime qualifiers out at first and ensure that it performs the basic find and exec command, and then add back in the mtime qualifiers. Because a reason why it might not see any files is because there are none to see.

I'm assuming by the way that you do have a:line in your code?

Further, there's also a link in my signature discussing how to put your code within [code][/code] markers to have it appear properly in a post.

I ran a modified variation of your script on my testcode directory and it worked fine:The result was:I also found that adding in the "-type f" and '-lht" terms cause no problems.

procfs's suggestion to add a debug statement between the first find and the second find is a good idea by the way, in fact you should add a statement before the sleep 3 and just after it to know that it's reached that second find command.

Are you saying that you never see the final "files listed" comment?

Hi,

Check this out...


#!/bin/bash

path1="/home/backup/newlogs/logs"
path2="/home/backup/softwares/mylogs/logs/"

echo "Listing files:-$path1"

find $path1/server.log.* -type f -mtime +90 -exec ls -lht {} \; && echo "Listing files:-$path2" && find $path2/server.log.* -type f -mtime +90 -exec ls -lht {} \;

echo "files listed"

exit


Hope this should work for you.

Just a side note here, in my experience, if you want to get help...
- don't DEMAND other people to solve your problem for you, and
- it helps if you are polite

Best regards

He added a print command between the two finds so you could see if the second find was simply not returning anything. It's called debugging.