From: | Tim Holloway <mtsinc(at)southeast(dot)net> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | All forked up |
Date: | 1999-11-19 19:47:13 |
Message-ID: | 3835A941.605E9B4D@southeast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I need some Unix guidance.
Foolishly or not, I designed the new PostgreSQL logging subsystem
to run as a process. It's forked off a function called by the
Postmaster main program right before the if(...)pmdaemonize
statements -- meaning that the shared memory enviroment has been
established, but the signals have not yet been attached.
When I issue the fork() call, it successfully creates a child process,
but the child is DOA. Investigation reveals a signal 5 trace/breakpoint
trap at the fork.
How do I prevent this? I presume you can mask it, but is that really
what I want to do?
TIA,
Tim Holloway
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-11-19 19:55:14 | Re: [HACKERS] 7.0 status request |
Previous Message | Jan Wieck | 1999-11-19 19:30:14 | New regression driver |