topic Re: Scripting question in Operating System - HP-UX

Scripting question

Adam Noble — Tue, 02 Sep 2008 09:56:27 GMT

Hi all,

This is quite an obscure question but would love to know how to do this. If I am writing a script which is interactive I want to show that the script is processing at certain points. In otherwords for example the script will say "Gathering Info....." what I wanted to know is how can I show the script is processing such as adding an additional dot every 10 secs. I hope this makes sense.

Cheers

Re: Scripting question

Steven E. Protter — Tue, 02 Sep 2008 10:24:42 GMT

Shalom,

while true
do
echo .
sleep 10
done

Lots of ways to do this.

SEP

Re: Scripting question

James R. Ferguson — Tue, 02 Sep 2008 10:31:53 GMT

Hi Adam:

To create a progress bar (dots, a spinning widget, etc.) in a shell script, you build a function that paints the bar with small sleep intervals between each point. You launch this piece as a background task while processing to do the real work of your script. When the real work is done, you kill the background process having captured its pid when you launched it.

Regards!

...JRF...

Re: Scripting question

Dennis Handly — Tue, 02 Sep 2008 11:39:45 GMT

You could do the reverse of JRF's solution and put the process the that does the work in the background and use SEP's sleep echo ".\c" to print out the dots.
You can use "kill -0 $SAVE_PID" (where you saved $! from the background job) to know when to quit the loop.

Re: Scripting question

Hein van den Heuvel — Tue, 02 Sep 2008 12:28:31 GMT

If you add a script to output dots then all you are showing is that the script outputting dots is making good progress at doing nothing.
If that helps your end users feeling better about the system, then fine.
Personally I would want to see honest progress otherwise I still need to resort to top or ps | grep to 'see' that it might be working.
Maybe a dot for each 10O MB processed? Or every 100 files compiled, every 1000 primes calculated, every 10,000 IOs does, every 5 seconds CPU burned, or whatever the task on hand might be

fwiw,
Hein.