On Wednesday 24 November 2004 10:03 am, Kevin Geiss wrote:
> you could try
>
> pgrep X
>
> at least it would be one less process forked and exec'd, compared to
> running ps and grep separately :)
>
> plus, you don't even have to parse its output, you can check its return
> status. (0 means there was a process whose name matched)
>
> pgrep is a pretty cool program you'll probably want to know about anyway,
> along with its sister pkill.
>
> and 'qpkg -f /usr/bin/pgrep' tells me it's in the procps package, so you
> probably already have it on your system.
<snip>
I don't have qpkg but this command works: rpm -qf /usr/bin/pgrep
Also rpm -ql pgrep lists all the files that are in that package
Jerry
--
Registered Linux User: 275424
Today's Fortune: Some parts of the past must be preserved, and some of the
future prevented
at all costs.
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)