Shell Programming and Scripting

Hi everyone, here's my problem. I have a script that runs in a infinite loop, repeating the same action in another script every 10 minutes. We need to monitor whether or not this loop script is running and be able to kill it should the need arise. However, the name of the script does not show up in the ps -efx listing, even though it is clearly running in the other window. Is there a way to make the script show itself in the ps -efx output, or get it's process ID?

Thanks!

if you know the pathname to your script....

fuser /path2yourScript

man fuser

at the start of the script ... get it to write it's PID into a readable file so you'll always know the PID you need to kill later as required ...

Code:

echo $$ > /tmp/script.PID

i am facing the same proble came u suggest me how to read it from a file once u read it and send it to a file

If the filename is as specified above, then

Code:

pid=`cat /tmp/script.PID`

Then use $pid to access the PID. E.g., to kill the process, do kill $pid

But if your system's ps command supports formatted output, with the -o swtich, you can use that instead of saving the PID in a temp file. Try ps -eo pid,args, and search the outpout to see if the name of your script shows up. The importnat thing here is using the args format (as an argument to the -o option). By default, ps outputs the command name as the comm format, which is a shortened form of the command that the system actually executes; the args format gives the full form of the command, which will include the name of the script.

thanks ...this willwork
but do we have asolution to this without the write read operation from a file

How do we make ps command display the scriptname that is running ?
wh does it show .sh and not complete scripname.sh.
if the scripname was there we could have found it by simple
ps and grep.
someone in the group suggested the reason for not didplaying scripting name
coud be that #!bash is not inlude in the running script /
any solution that way

I would not suggest building a solution that involves a script running an infinite loop. Why not loop until a "stop" file is found, e.g...

Code:

until [[ -f /tmp/stopfile ]]
do
  :
  sleep 600
done
rm /tmp/stopfile

Instead of killing the script, it can be stopped by using:

Code:

touch /tmp/stopfile