Message-ID: <4F686965.5060306@sympatico.ca>
Date: Tue, 20 Mar 2012 07:26:29 -0400
From: Frank Bax <fbax@sympatico.ca>
User-Agent: Mozilla/5.0 (X11; OpenBSD amd64;
	rv:5.0) Gecko/20110805 Thunderbird/5.0
MIME-Version: 1.0
CC: pgsql-sql@postgresql.org
Subject: Re: Setting the process title, or can I?
References: 
 <CAKwGa_9MOQ1zsFaXcdyaCqbPUNDXhMHPOzpo1SSxME8a5YJ2UA@mail.gmail.com>
In-Reply-To: 
 <CAKwGa_9MOQ1zsFaXcdyaCqbPUNDXhMHPOzpo1SSxME8a5YJ2UA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On 03/20/12 06:14, B=C3=A8rto =C3=ABd S=C3=A8ra wrote:
>So as a dirty and quick hack to
> make sure our failure filter works I wanted to have an external process
> kill and relaunch the filter from cron each 30 minutes.
>
> Is there anyway I can mark the process running the filter, maybe using
> the update_process_title feature? I'd like to have something I can see
> from a ps command, grep for it and kill -15 it, without wasting our
> scarce resources on one more pg process to use info from pg_stat_activi=
ty.


Change your filter so it only runs once; not in a forever loop; then add=20
the filter to cron to run every minute.

If this new filter continues to freeze; then use pkill to get rid of it.
Hopefully RHEL has a pkill command which works like (ps | grep | kill).