Sub-processes cost time in shell scripts - try using a case instead of the multiple if [...] statements - case is a built-in and is thus far faster than the sub-processes necessary to execute if [...].
Maybe something (untested) along the lines of...
>$1.out
unset stat int cpu scpu
echo "Starting rebuild of $1 into $1.out"
while read line ; do
case $line in
END)
cpu=`expr $cpu / 60`
# Write data line
echo "$int,$cpu" >>$1.out
unset stat int cpu scpu
rec=`expr $rec + 1`
echo "`date`:Wrote record: $rec"
;;
*GMT | \
*SAST)
int=`echo $line|cut -c12-16`
;;
vmstat\ 2\ 60:)
stat=1
;;
procs |\
avm)
:
;;
*)
scpu=`echo $line | awk '{ print $16 "+" $17 }'|bc`
cpu=`expr $cpu + $scpu`
;;
esac
done < $1
echo "Complete!"
HTH ,
A user level that continues to overstate my experience :-))
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|