Industry guru Dave Taylor offers free tech support on a wide variety of technical and business topics, including HTML, Apple iPhone, online advertising, Cascading Style Sheets, Web design, management, Unix, Linux, search engine optimization, online dating, Mac OS X, shell script programming and Microsoft Windows.

How can I run an app if another app is running?

I need to run a Unix application if a different application is running, from within a shell script. How do I do this?

Dave's Answer:

If you know the name of the application and you are sure that only instantiation of it can be running at a given time, then the solution is pretty simple:

running="$(ps -aux | grep yourappname)"

if [ -n "$running" ] ; then
   launch your secondary application
fi

Obviously, you'd need to change 'yourappname' to the appropriate name of the app you seek, but that's all you need to do.

If you could have more than one version of the process running or otherwise don't have an easy way to identify it uniquely, then you have a greater challenge. For example, if you wanted to check for the Apache Web server (process name "httpd") but wanted to make sure that you weren't seeing a child process but the parent, then you'd also need to take into account the parent process ID (ppid) because the ppid of child processes is the parent process (which makes sense!): in the case of child Apache processes, their ppid's are the process ID (pid) of the parent Apache process.

And that's exactly how you do it. Use a flag like '-j' to get the pid and ppid, use grep to pull out the matching processes by name, then check the ppid to identify which has the odd ppid out. Let me show you. Here's a set of processes shown in this format:

$ ps -jax | grep http
root    6706     1     0 Ss    ??    0:03.43 /usr/local/apache/bin/httpsd
www     6707  6706     0 I     ??    0:11.91 /usr/local/apache/bin/httpsd
www     6708  6706     0 S     ??    0:13.22 /usr/local/apache/bin/httpsd
www     6709  6706     0 S     ??    0:13.46 /usr/local/apache/bin/httpsd
www     6710  6706     0 I     ??    0:13.82 /usr/local/apache/bin/httpsd
www     6711  6706     0 S     ??    0:12.36 /usr/local/apache/bin/httpsd
www    19003  6706     0 S     ??    0:00.09 /usr/local/apache/bin/httpsd
www    19046  6706     0 I     ??    0:00.01 /usr/local/apache/bin/httpsd
www    19429  6706     0 S     ??    0:00.02 /usr/local/apache/bin/httpsd
www    19432  6706     0 S     ??    0:00.04 /usr/local/apache/bin/httpsd
www    19531  6706     0 I     ??    0:00.00 /usr/local/apache/bin/httpsd
www    19612  6706     0 S     ??    0:00.01 /usr/local/apache/bin/httpsd
www    19615  6706     0 S     ??    0:00.00 /usr/local/apache/bin/httpsd
www    19616  6706     0 S     ??    0:00.00 /usr/local/apache/bin/httpsd
www    19622  6706     0 S     ??    0:00.01 /usr/local/apache/bin/httpsd
www    19624  6706     0 Z     ??    0:00.00  (httpsd)

Notice that the second column is the process ID and the third is the parent process id: as you can see, the parent process is 6706 in this instance.

You can identify this in your script (I've written about it here before) and then screen for a process by ID rather than by name (use the '-p process' flag to ps) then use the same basic test shown earlier to launch your secondary application, as needed.

Hope that helps you out!

Help others find this article at Del.icio.us, Digg, Netscape, Reddit, and Stumble Upon

Subscribe!

Never miss another useful Q&A article again! Subscribe to AskDaveTaylor with Google Reader.

Comments

The first simple solution won't work.

On all Unix boxes that I have ever used,

running="$(ps -aux | grep yourappname)"

will match the grep in addition to yourappname, running will always be non-zero length and whatever is in the if will always run.

There are a could of ways of dealing with this. You can either pipe the grep into a second grep -v

running="$(ps -aux | grep yourappname | grep -v grep)"

or use brackets on the appname

running="$(ps -aux | grep [y]ourappname)"

Both of these will remove the grep process from running, but
either case will fail if there is also an application called yourappnamemonitor or such that would cause the grep to succeed even if the process that you were interested in wasn't running.

Posted by: Ray at January 9, 2006 2:22 PM

use pgrep instead :

if pgrep name >/dev/null ; then echo "running";done

even better is to launch the process and save the PID so you don't have to guess, like this :

program &
mypid=$!

then to check if the process is running, you can use:
if kill -0 $mypid ; then echo "running"; done

Posted by: monsieur at May 17, 2006 5:00 AM

I have a lot to say, but ...

I have a lot to say, and questions of my own for that matter, but most of all I'd like to say thank you for all your efforts on this Web site by buying you a chai!

I do have a comment, now that you mention it!