[Linux]Anyone know where I can get a program called pidof?

[Fallon]

I'm trying to write a script that'll check if a process is running. I searched around on the net for one and i found a php script that seems to work, but it requires a command called pidof. I've searched around but I haven't been able to find it yet so I figured I'd ask. Thanks.

[Fallon]

Arg, nm this. I musta fat-fingered it and typed in the wrong thing. I found it on RPMFind.net. For those interested, it along with some other tools are at http://rpmfind.net/linux/rpm2html/se...hp?query=pidof

This'll be a fun update..prollay more then likely gonna break somethin.

[bendsley]

Should probably be on the cd of the distribution you used.

[Silvy]

Originally Posted by Fallon

I'm trying to write a script that'll check if a process is running. I searched around on the net for one and i found a php script that seems to work, but it requires a command called pidof. I've searched around but I haven't been able to find it yet so I figured I'd ask. Thanks.

The more common way is to check for a pid file of the process.
I don't know wether you have access to the script you're trying to detect, or it's pid file, but if I were to write both, I'd use a pid file

=> a pid file, is a file at a specified location (that you can check) that has the pid (process identifier) of the script that is running. Checking the file gives you the pid.

Probably lot's of situations where this solution won't fly, but I thought I'd drop the idea anyway

[GoogleMeister]

how about: "ps -ef | grep <processID or processname>" imbedded into the code. If no lines returned, then you can be pretty sure that it ain't runnin'. I have run into situations where I needed to know not if a process was running, but rather how many instances were running. For that I shell scripted "ps -ef | grep <processID or processname> | wc -l".

Maybe a bit off track, but I hope it helps.

[rukkyg]

$ ls -l /sbin/pidof
lrwxrwxrwx    1 root     root            8 May  6  2003 /sbin/pidof -> killall5

pidof links to killall5 which is from the sysvinit package (http://freshmeat.net/projects/sysvinit).

if you already have killall5 (ls /sbin/killall5) you can just link it with

# ln -s /sbin/killall5 /sbin/pidof

[Fallon]

Originally Posted by rukkyg

$ ls -l /sbin/pidof
lrwxrwxrwx    1 root     root            8 May  6  2003 /sbin/pidof -> killall5

pidof links to killall5 which is from the sysvinit package (http://freshmeat.net/projects/sysvinit).

if you already have killall5 (ls /sbin/killall5) you can just link it with

# ln -s /sbin/killall5 /sbin/pidof

Dude, I love you...you just made my life so much easier.
Thank you a bunch and thank you to everyone else who offered other solutions.

[Latch]

Originally Posted by GoogleMeister

how about: "ps -ef | grep (processID or processname)" imbedded into the code. If no lines returned, then you can be pretty sure that it ain't runnin'. I have run into situations where I needed to know not if a process was running, but rather how many instances were running. For that I shell scripted "ps -ef | grep (processID or processname) | wc -l".

Maybe a bit off track, but I hope it helps.

Unless it catches it's own grep.... I've run into that often enough.

latch@afx:~$ ps -ef | grep tomato
latch    24337 24325  0 18:12 pts/457  00:00:00 grep tomato
latch@afx:~$

gotta grep out the grep.. i.e.:

ps -ef | grep proccessIDorprocessName | grep -v grep

Then you can pipe to wc -l or whatever you'd like hehe.

latch@afx:~$ ps -ef | grep bash
latch     8370     1  0 Aug12 ?        00:00:00 /bin/bash /usr/bin/thunderbird
latch    25518     1  0 Aug14 ?        00:00:00 /bin/bash ./restartScript
latch    24020     1  0 17:59 ?        00:00:00 /bin/bash /usr/bin/firefox
latch    24325 24323  0 18:12 pts/457  00:00:00 -bash
latch    24434 24325  0 18:15 pts/457  00:00:00 grep bash
latch@afx:~$ ps -ef | grep bash | grep -v grep
latch     8370     1  0 Aug12 ?        00:00:00 /bin/bash /usr/bin/thunderbird
latch    25518     1  0 Aug14 ?        00:00:00 /bin/bash ./restartScript
latch    24020     1  0 17:59 ?        00:00:00 /bin/bash /usr/bin/firefox
latch    24325 24323  0 18:12 pts/457  00:00:00 -bash
latch@afx:~$ ps -ef | grep bash | grep -v grep | wc -l
4
latch@afx:~$

[roboshark]

use a script like this:

#!/bin/sh

proc=${1}
if [ -z ${proc} ]; then
echo "usage: $0 process_name";
exit 1;
fi
ps ax | awk "\$5 ~ /$proc/ { print \$0 }"

Alternatively, use "print \$1" instead of the final "print \$0" to print only the actual PID.

[rukkyg]

Originally Posted by Fallon

Dude, I love you...you just made my life so much easier.
Thank you a bunch and thank you to everyone else who offered other solutions.

I Love you too. Let's get a pizza.

[bacon]

[jrw@thorin jrw]$ rpm -qf /sbin/pidof
SysVinit-2.84-2

If you are using a redhatish distribution, it'll be in the SysVinit package.

[Fallon]

Originally Posted by rukkyg

I Love you too. Let's get a pizza.

k, you're buying then cause I can't afford it.

[GoogleMeister]

Originally Posted by Latch

Unless it catches it's own grep.... I've run into that often enough.

latch@afx:~$ ps -ef | grep tomato
latch    24337 24325  0 18:12 pts/457  00:00:00 grep tomato
latch@afx:~$

gotta grep out the grep.. i.e.:

ps -ef | grep proccessIDorprocessName | grep -v grep

Then you can pipe to wc -l or whatever you'd like hehe.

latch@afx:~$ ps -ef | grep bash
latch     8370     1  0 Aug12 ?        00:00:00 /bin/bash /usr/bin/thunderbird
latch    25518     1  0 Aug14 ?        00:00:00 /bin/bash ./restartScript
latch    24020     1  0 17:59 ?        00:00:00 /bin/bash /usr/bin/firefox
latch    24325 24323  0 18:12 pts/457  00:00:00 -bash
latch    24434 24325  0 18:15 pts/457  00:00:00 grep bash
latch@afx:~$ ps -ef | grep bash | grep -v grep
latch     8370     1  0 Aug12 ?        00:00:00 /bin/bash /usr/bin/thunderbird
latch    25518     1  0 Aug14 ?        00:00:00 /bin/bash ./restartScript
latch    24020     1  0 17:59 ?        00:00:00 /bin/bash /usr/bin/firefox
latch    24325 24323  0 18:12 pts/457  00:00:00 -bash
latch@afx:~$ ps -ef | grep bash | grep -v grep | wc -l
4
latch@afx:~$

Ahhhhh... The vageuries of different shells, systems and utilities. How many things in hte Windows world spawn such great conversation?

[Latch]

All part of the fun of having total control