> (gdb) bt
> #0 0x4013da02 in __libc_accept () from /lib/libc.so.6
> #1 0x80c34b9 in StreamConnection ()
> #2 0x80e07b1 in ConnCreate ()
> #3 0x80e0239 in ServerLoop ()
> #4 0x80dfdb3 in PostmasterMain ()
> #5 0x80c3fa5 in main ()
> #6 0x400a39cb in __libc_start_main (main=0x80c3ec0 , argc=
Hi
Once more, this time with feeling :)
Sorry, not a regular user of gdb, but I figured out my error, does this
help?
Anything else before kill -9?
thanks,
PHilip
# gdb postmaster 29214
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU Gen
Hi
Not sure if this is helpful, but...
Am I doing this correctly, anything else to try before "pulling the plug"?
thanks,
PHilip
# gdb postmaster 29214
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 11 May 2001 10:26, Philip Crotwell wrote:
> PS I don't know why this happened, but the only theory I have is that I am
> running with -i to allow jdbc connections and I had port scanned the
> machine with nmap shortly before noticing that I
Philip Crotwell <[EMAIL PROTECTED]> writes:
> I am running postgres7.1 on redhat 6.2 and my database has gone belly up.
> I know i am not supposed to "kill -9 " the postmaster, but it has become
> completely unresponsive. pgsql just hangs as does stopping with the
> rc.d script.
Actually, kill -
