From: Christopher Browne <cbbrowne@acm.org>
Subject: Re: How to check postgres running or not ?
Date: Sun, 19 Sep 2004 21:33:00 -0400
Organization: cbbrowne Computing Inc
Lines: 31
Message-ID: <m3llf5pvw3.fsf@wolfe.cbbrowne.com>
References: <414A7395.8070503@vertex.co.in> <414CE76E.2050405@noggon.com>
	<414D7533.10708@3times25.net> <19430.1095611100@sss.pgh.pa.us>
	<414DF2D5.5040509@bigfoot.com> <414E25B3.9070309@noggon.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity,
	linux)
Cancel-Lock: sha1:qbXQwwDosLGyoVMhvCfecMSs/Po=
To: pgsql-sql@postgresql.org

Clinging to sanity, worik@noggon.com (Worik) mumbled into her beard:
> [snip]
>> Just to enforce the test is better looking for the entire executable
>> path:
>>         ps aux | grep /usr/bin/postmaster | grep -v grep
>>
>
> Does not work for me!
>
> worik@stolberg:~$ ps aux | grep /usr/bin/postmaster | grep -v grep
> worik@stolberg:~$ ps aux | grep postmaster | grep -v grep
> postgres   670  0.1  0.6  8544 1688 pts/1    S    12:33   0:00
> /usr/lib/postgresql/bin/postmaster
> worik@stolberg:~$
>
> So...
> " ps aux | grep postmaster | grep -v grep "
> is more reliable(?)

There's a very slightly clever modification that gets rid of the extra
grep...

Try.. 

 [appropriate ps command for your platform] | egrep '[p]ostmaster'

That egrep _won't_ match its own command line.
-- 
let name="cbbrowne" and tld="ntlug.org" in String.concat "@" [name;tld];;
http://www3.sympatico.ca/cbbrowne/multiplexor.html
He doesn't have much of a reputation, or so I've heard.