Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 /
От | Jason Tishler |
---|---|
Тема | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |
Дата | |
Msg-id | 20030505121301.GE556@tishler.net обсуждение исходный текст |
Ответ на | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / (Frank Seesink <frank@mail.wvnet.edu>) |
Ответы |
Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 /
Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |
Список | pgsql-cygwin |
Frank, On Fri, May 02, 2003 at 06:11:06PM -0400, Frank Seesink wrote: > More info: > > * Reset everything to the way things 'normally' would be (user > 'postgres' only a member of 'Users', ipc-daemon configured to run as > Local System account, etc.). > [snip] > * Switched out and logged in as 'postgres', brought up BASH, and tried > 'ipctest s', and failed as usual. > * Did a 'ps' and saw only the shell and the ps command...no ipc-daemon. Did you do a "ps" or a "ps -ef"? With the former, ipc-daemon should not be displayed since it was running under a different user. > * For fun, tried 'ipc-daemon &', and it fired up! YA truly amazing occurrence. The above should have failed as follows: $ ipc-daemon (ipc-daemon) IPC-daemon is already started !! > [snip] > > It's as if the copy of ipc-daemon running in the 'postgres' context is > oblivious to the copy running as Local System account. Yes. I believe understanding the above will lead to the root cause of this problem. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
В списке pgsql-cygwin по дате отправления: