All forked up

Поиск
Список
Период
Сортировка
От Tim Holloway
Тема All forked up
Дата
Msg-id 3835A941.605E9B4D@southeast.net
обсуждение исходный текст
Ответы Re: [HACKERS] All forked up  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: wieck@debis.com (Jan Wieck)
Дата:
Сообщение: New regression driver
Следующее
От: wieck@debis.com (Jan Wieck)
Дата:
Сообщение: Re: [HACKERS] 7.0 status request