Re: killing process question

--thanks for the reply:

--no, I don't see anything like that. this is what I have:

[snip]

postgres 3488 5.6 0.0 11412 4 pts/4 T Sep18 88:53 postgres: joe
testdb 16.xx.xx.xx SELECT

[/snip]

--this tells me that this proc had been running once upon a time (since the
18th) and
--has stopped (the 'T'). the user has said that he had since killed the
tool
--that connected to the database and booted his machine.

--so ... when I do a 'kill pid' or 'kill -TERM pid' ... *poof* ... nothing
happens ...

--what am I missing?

-X

-----Original Message-----
From: Søren Neigaard [mailto:s(dot)neigaard(at)mobilethink(dot)dk]
Sent: Thursday, September 19, 2002 10:32 AM
To: Johnson, Shaunn
Subject: SV: [GENERAL] killing process question

Are you sure they are just hanging around, it could be a connection pool
that keeps those processe running!? Du you use a
connectionpool/databasepool?

/Søren

-----Oprindelig meddelelse-----
Fra: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org]På vegne af Johnson, Shaunn
Sendt: 19. september 2002 16:09
Til: pgsql-general(at)postgresql(dot)org
Emne: [GENERAL] killing process question

Howdy:

Running PostgreSQL 7.2.1 on RedHat Linux 7.2 kernel 2.4.7.

I have some processes that are just hanging around and I'm
trying to kill them. I know I'm not supposed to use
'kill -9 pid', but when I try to use 'kill -TERM pid'
nothing happens.

How can I safely and effectively kill a process that is
too stubborn to go away?

-X