X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 56FFE5423F for ; Sat, 23 Apr 2005 15:38:51 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 59312-08 for ; Sat, 23 Apr 2005 18:38:40 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 77BA6542E8 for ; Sat, 23 Apr 2005 15:38:38 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j3NIccCC060902 for ; Sat, 23 Apr 2005 18:38:38 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j3NIDbCI055984 for pgsql-admin@postgresql.org; Sat, 23 Apr 2005 18:13:37 GMT (envelope-from news) From: Christopher Browne X-Newsgroups: pgsql.admin Subject: Re: Killing Processes Date: Sat, 23 Apr 2005 14:00:11 -0400 Organization: cbbrowne Computing Inc Lines: 37 Message-ID: References: <399c5204777051febd1e3432d981b03b@sitening.com> <20050423161641.GA40259@winnie.fuhr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:eQ6zDvxozyTqni2fOOOQEcCsjPU= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200504/345 X-Sequence-Number: 17358 In the last exciting episode, mike@fuhr.org (Michael Fuhr) wrote: > On Sat, Apr 23, 2005 at 10:58:46AM -0500, Thomas F.O'Connell wrote: >> >> It is generally not recommended that you kill processes with anything >> stronger than HUP, which is (I believe) what kill sends by default. > > kill usually sends TERM by default, not HUP. > > (I say "usually" only because I haven't personally examined every > implementation of kill in existence. Every one I've used sends > TERM by default and I haven't heard of any that work otherwise.) The only "normative" standard that would seem meaningful would be POSIX. A quick "google" doesn't find anything relevant there. The most relevant thing is pointers to the GNU utilities, which is where the "kill" used on Linux comes from. The man page for that indicates TERM as the default, and later has pointers to POSIX.1 as its 'source of authority.' I'd hazard the guess that perhaps that default was declared in POSIX, which is at least a form of standard. It may not be normative for BSD, but it is still instructive... Have you ever had a "bad day" when you issued "kill -3" rather than "kill 2"? I have also had the day when part of me wanted "kill it now; kill -3", another part knew "No, you should just use kill -2, and wait...", and my treacherous fingers wound up taking the wrong side in the conflict ;-). -- "cbbrowne","@","ntlug.org" http://cbbrowne.com/info/internet.html Rules of the Evil Overlord #144. "I will order my guards to stand in a line when they shoot at the hero so he cannot duck and have them accidentally shoot each other. Also, I will order some to aim above, below, and to the sides so he cannot jump out of the way."