topic Re: ksh script - echo to screen even though app is not done in Operating System - HP-UX

ksh script - echo to screen even though app is not done

Ratzie — Tue, 10 Mar 2009 01:39:33 GMT

I have a script that calls different commands.
And writes to screen.

But the first command, takes about 2 minutes to run, and the script goes on to the next two commands.

I want it to wait until the first command to finish before it goes on to the next, and echo it to the screen.

#!/bin/ksh -p

# Stop the application commands:
echo Disabling xxx application...
/opt/app/application/shutdown
(here is where I want it to wait, or maybe output # every 10 seconds...)
echo xxx application -- disabled
echo

echo Disabling yyy application...
/opt/app/application2/stopapp
echo yyy application -- disabled
echo

Re: ksh script - echo to screen even though app is not done

Mark McDonald_2 — Tue, 10 Mar 2009 02:01:49 GMT

What is in this script:
/opt/app/application/shutdown

Maybe this fires off some background shutdowns and return to you before it is complete.

One method would be to loop and monitor for the processes that are shutting down. Check every 10 seconds and echo the "#" then exit the loop once the processes are gone.

good luck

Re: ksh script - echo to screen even though app is not done

Suraj K Sankari — Tue, 10 Mar 2009 03:54:41 GMT

Hi,

As per your script every thing are looks ok. Check your â /opt/app/application/shutdownâ script
if your /opt/app/application/shutdown script is having any & which means run the job in background and execute the next line.
So check your /opt/app/application/shutdown script and delete the &

Suraj

Re: ksh script - echo to screen even though app is not done

Mark McDonald_2 — Tue, 10 Mar 2009 04:37:10 GMT

Before simply deleting the "&" in the shutdown script, is this an application with lots of processes?

The shutdown script may separately end these processes and removing the "&" will make the script wait for each single process to end before stopping the next process. This could seriously slow the whole process.

A loop in the monitoring script would definitely be better in this case.

Re: ksh script - echo to screen even though app is not done

Laurent Menase — Tue, 10 Mar 2009 08:09:25 GMT

if you know the pid of your application and want to check it is still there you can use
while :
do
kill -0 $pid 2>/dev/null||break
sleep 1
done

kill -0 fails if the process doesn't exist anymore

Re: ksh script - echo to screen even though app is not done

Mark McDonald_2 — Tue, 10 Mar 2009 22:49:46 GMT

Ratzie

Has this helped? How about some points?

Re: ksh script - echo to screen even though app is not done

Ratzie — Tue, 10 Mar 2009 23:45:25 GMT

I was looking at possibly...
while
do
ps -ef|grep app
echo #
done

But I dont know the syntax....

Re: ksh script - echo to screen even though app is not done

James R. Ferguson — Tue, 10 Mar 2009 23:54:10 GMT

Hi:

> I was looking at possibly...
> while
> do
> ps -ef|grep app
> echo #
> done

while true
do
PID=$(UNIX95= ps -C app -o pid=)
echo "I see ${PID}"
done

Note the whitespace after UNIX95= . This keeps the setting only for the duration of the command line so that it only applies to the 'ps'. The 'pid=' argument says to suppress a header line and just report the process (if any) whose basename matches "app". This is the truly safe way to find a process by name in HP-UX.

Regards!

...JRF...

Re: ksh script - echo to screen even though app is not done

Roland Piette — Wed, 11 Mar 2009 11:18:40 GMT

Hello Ratzie,

Try this following :

PID=`/opt/app/application/shutdown &`
wait $PID

At this step you script will wait until detached process shudown ends.

Good luck,
Roland