UNIX for Dummies Questions & Answers

stmt_cnt=$(ls -1 ${1}/${2}|wc -l)
if [ ${stmt_cnt} -ne 0 -a ${stmt_cnt} -lt 501 ]; then
out_str="${out_str}\n$(date +"%Y%m%d%H%M%S"): Moving ${stmt_cnt} \"${2}\" statements from ${1} to ${3}\n"
find ${1} -name "${2}" | sort -t"_" +7n +8n | xargs ksh -c 'mv $* '"${3}" foobar
fi

Agreed, foobar is confusing here but works so syntax is not an issue

$1 = starting directory
$2 = pattern
$3 = destination

Originally Posted by methyl

The script needs urgent revision because it has some serious problems which may not produce syntax errors or error messages (?) but which cause alarming process anomalies due to command truncation in AIX. Have you counted the number of input files and compared with the number of output files?
I would suggest avoiding any unlimited xargs in AIX and executing comands one-by-one. Credit: Scrutinizer picked up on this.

Yes, this script is working in production as intended.

Code:

stmt_cnt=$(ls -1 ${1}/${2}|wc -l) 
   if [ ${stmt_cnt} -ne 0 -a ${stmt_cnt} -lt 501 ]; then
     out_str="${out_str}\n$(date +"%Y%m%d%H%M%S"): Moving ${stmt_cnt} \"${2}\" statements from ${1} to ${3}\n"
     find ${1} -type f -name "${2}"|while read filename
     do
                mv "${filename}" "${3}"
     done
  fi

FYI.. -type f is not required

I have no idea what the sort is for and IMHO the ksh command line with the foobar is a botch to lose a surplus parameter when the command line is too long.
You clearly did not write this script but it is hard to justify that this script works despite the absence of reported syntax or other error messages.

Sorry to be so abrupt but that ksh line is a real problem.



Are you really sure? I'm not so sure.

Did you try out before asking ? As I mentioned , it's working for years in PRODUCTION how can you blame the syntax.

Let's assume that $3 is a pre-existing writeable directory. We don't know anything about $2, but that could be the subject of the next post.