From: | Jason Tishler <jason(at)tishler(dot)net> |
---|---|
To: | Frank Seesink <frank(at)mail(dot)wvnet(dot)edu> |
Cc: | Pgsql-Cygwin <pgsql-cygwin(at)postgresql(dot)org> |
Subject: | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |
Date: | 2003-05-05 11:25:37 |
Message-ID: | 20030505112537.GA556@tishler.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin |
Frank,
On Fri, May 02, 2003 at 05:37:11PM -0400, Frank Seesink wrote:
> Ok, looks my non-attachment attempt worked. So I'll repeat something I
> asked in private:
>
> I have spent the better part of the afternoon digging back thru the last
> 4 months of postings. One thing caught my eye.
>
> Jason, you mention repeatedly about a file
>
> /tmp/cygipc_0
>
> But I have yet to see that file on XP (where PostgreSQL is NOT working)
> _OR_ Windows 2000 (where the exact same install IS working). All I see
> are the /tmp/MultiFile* files.
>
> Is this file you mention still valid now?
Yes.
> And if so, how do you explain the Windows 2000 box working properly?
> I'm confused.
See below...
> Or does the /tmp/cygipc_0 only show up when postmaster itself is run,
Yes, when postmaster calls shmget().
> kind of like a PID file or other filelocking mechanism?
No, this file is used by cygipc's SysV shared memory implementation.
> Please note I have only been working thus far with the test command
> 'ipctest s' and the 'initdb' command. I have yet to fire up postgres
> itself yet.
The above explains why you have not seen this file yet.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Tishler | 2003-05-05 11:30:59 | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |
Previous Message | Frank Seesink | 2003-05-02 22:42:14 | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |